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
Please consider making the network bindings of the VNC service configurable, so that one can prevent it from being exposed in potentially untrusted networks. Maybe this could be realized by a checkable list of the current networks/IP addresses (including localhost, for instance if one wants to employ some tunneling technology for making the service externally accessible).
Thanks in advance! ;-)
The text was updated successfully, but these errors were encountered:
Sorry, you are right! Localhost just did not show up in the list of network bindings after starting the VNC server, but connecting with a vnc client to localhost actually works! ;-)
bk138
changed the title
[Feature request] Please make network bindings configurable and add binding to localhost
[Feature request] Please make network bindings configurable
Oct 12, 2021
Please consider making the network bindings of the VNC service configurable, so that one can prevent it from being exposed in potentially untrusted networks. Maybe this could be realized by a checkable list of the current networks/IP addresses (including localhost, for instance if one wants to employ some tunneling technology for making the service externally accessible).
Thanks in advance! ;-)
The text was updated successfully, but these errors were encountered: