You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VNC needs an SSH/HTTP like service that runs as root and spawns sessions as the authenticating user allowing the VNC protocol to be tunnelled to the correct session via a single TCP port.
The sessions should remain available on disconnect and be re connected on re authentication by a user.
Having to run up a new server with a new port number for each user is an administrative and firewall unfriendly process.
#160 has this scheme implemented/designed in a safe manner using SSH as the transport and local UNIX sockets to separate users, pending any review/feedback from TigerVNC developers.
You can use the supplied scripts and patches to test it out if you want to.
VNC needs an SSH/HTTP like service that runs as root and spawns sessions as the authenticating user allowing the VNC protocol to be tunnelled to the correct session via a single TCP port.
The sessions should remain available on disconnect and be re connected on re authentication by a user.
Having to run up a new server with a new port number for each user is an administrative and firewall unfriendly process.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: