On 2/25/24 06:35, Jonathan Billings wrote:
What this means is there’s no TCP port listening for Xvnc, just a UNIX
socket file. So two people or a local and remote session can’t have
sessions interfering with each other. I played with using systemd socket
activation too but that’s too complicated for this post.
Then, for remote connections, I would forward the UNIX socket with SSH.
If you are using a VNC client that doesn’t support UNIX sockets, you can
tell OpenSSH to forward a remote socket to a local TCP socket, but you
can also forward a remote to local socket to use with tigervnc’s client
in Fedora. The great thing about it is that there’s never a listening
tcp port on either side of the connection except ssh.
When it’s set up, it’s just like having a remote VNC session with the
upstream systemd units, but it doesn’t need a listening TCP port
assigned to each user.
It's a valid option, but I don't see how it's relevant to this issue.
There's no port conflict.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
