Session Manager behaviour with UDS listening sessions about turbovnc HOT 4 CLOSED

It definitely does not work at the moment. I'll scope it out and see if it is something I can implement easily or whether it will require extensive modifications.

from turbovnc.

Thank you for the swift reply! I don't know if it's relevant, but the following works:

• having ssh key auth setup and working with server
• start an UDS session on server
• using "my_server_fqdn::/path/to/socket" in the Viewer

=> this shows the VNC auth window and access can proceed. If I understand correctly, in this case the session manager is not involved.

from turbovnc.

Yes, you can use Unix domain sockets without the session manager. The session manager itself, however, still assumes that the session will be listening on a TCP port corresponding to its X display.

from turbovnc.

In order to successfully generate an OTP for and connect to a TurboVNC session listening on a Unix domain socket, the TurboVNC Session Manager would need to know both the X display number of the session and the UDS on which it is listening. That would require extending the session manager protocol. Also, since Unix domain socket support requires an external SSH client, the session manager would need to be extended to handle external SSH clients. Otherwise, the built-in SSH client would be used for the session manager connection, and the external SSH client would be used for the RFB connection. I have added UDS support as a sub-feature of #148.

I did at least fix the warning.

from turbovnc.