![]() Session keeps running when you disconnect - can be handy for users, or in some situations a pain for admin or securityĬan be useful for multi-user setups. ![]() (and could be done via VPN-style network)įairly simple (e.g. More involved (various configs, networking details) Next to impossible over WAN, at least without VPN (and SSH may be simpler than VPN). Some SSH servers disable X by default and your admin may have to configure it.Īvoids SSH overhead. Security (auth and encryption) is already handled. Good (draw commands, small lag for encryption) Nearly none (assuming exising SSH server) This has become more relevant as GUIs have become more fanciful and become less network-friendly Such wrappers may also deal better with a bulk of graphical changes, because unlike bare X, they could choose to aggregate such changes and/or not send you all graphical updates. If you want a remote X session that persists between (re)connections, look at ways of wrapping it - VNC, NX, Xpra, etc. ![]() So remote X makes less sense over over wifi or larger distances. The connection and the session are transient, Which were all connected to a single beefy server that ran the actual programs for one or two dozen such dumb terminals Use mostly dumb terminals, meaning cheaper hardware that could do little more than display things There was a period where networked X on a LAN was a sensible way to set up a certain kind of computer lab: something on the local LANīut often actually a SSH tunnel, because this is the easiest way to securely get around the sensible firewalling of such connections.ĭISPLAY value will be something like localhost:10.0 (localhost due the the way SSH tunneling works) Remote: you log into a remote machine, you tell an app on the remote machine to contact your local X server over the network. refer to a local displayĪ number of modern extensions will only work when run locally - notably hardware related ones, such as GPU features. On your local machine, the X server is on the same machine, and you skip the networkingĭISPLAY values of :0, :1, etc. X is an inherently networked protocol (.even if locally it has graphical extensions that do not network efficiently).Įach X application is an X client that you can connect to any X server (the thing that draws things for you) over the network. 9.1.4 Example using Cygwin/X (windows) as a client.2.5.4 Ultravnc forgets password, and other settings (WinXP).2.5.3 "Unknown authentication scheme from VNC server: 18" (Remmina).2.5.2 "Server did not offer supported security type" / "No matching security types" / "No security types supported" / "Unknown authentication scheme from VNC server".2.5.1 Black right half in multi-monitor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |