![]() ![]() For example I could launch the default GNOME session on EL7 remotely without running an insecure VNC TCP server on localhost exposing it to other users. The first option to run xinit session (persistently or closing on disconnect) is the one that I personally like to use on a server if I want to run some GUI utilities on it. Allow the client to connect to any VNC server that the remote is able to access over TCPĪll of the options can be done by passing different kinds of parameters from viewer when the helper is executed remotely.Allow the client to connect to a local VNC server (on the remote) listening on a TCP socket (localhost:5900+).Optionally have the session automatically close when the client disconnects.Persistently and securely run a xinit session with Xvnc (UNIX sockets used internally).The server side helper can do the following things: This design relies on client implementation in vncviewer with libssh2 that can execute the helper program on the server to do some proxying for it. VNC over SSH solved this problem by using the exec channel of SSH as a secure transport of VNC data. Running applications and full X sessions remotely on a headless system that has Xvnc installed is somewhat complex and insecure usually glued together with port forwarding to localhost. This also contains a more complete design. The UNIX socket issue became a playground for my VNC over SSH design so I've moved the discussion to its own issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |