I have reported a bug to the Vino project, both upstream and in launchpad about this issue look there for more details. For what I know, only the Linux-based vinagre viewer supports it. The problem surfaced when the Vino project decided to switch to require encryption by default - unfortunately, the only kind of encryption supported by the vino server (type 18) is not supported by most of the Windows, Android, and iOS viewer. Partial answer: (posted for sake of helping other people, NOT RECOMMENDED) I hope there will be other answers to the question - I will mark this answer as the right one as there are no solution by now).
#Tigervnc no matching security types mac install#
On Windows: Install the binary client from here.Ĭonnect and enjoy a (slowish.) encrypted connection.
I am using port 6000 to not mess with vino).
Do not use a passphrase on the generated SSL certificate. (you will have to put the last one in one of your login startup scripts, or whatever. X11vnc -forever -repeat -usepw -ssl -autoport 6000 On Linux (follow the instruction that x11vnc is giving you, is verbose but worth reading): x11vnc -storepasswd You need a bit of expertise to make it work, so terse instruction here: Real solution: I am now using SSVNC on the windows machine and x11vnc on the linux server. The Question: until TightVNC (and the rest of the world) catches up, is it possible to configure the internal VNC server to use the previous Security Type?
#Tigervnc no matching security types mac update#
The diagnosis: It seems that the update changed the security type to a new one not known by tightVNC (it happened in the past). The "sharing" part is configured as it should, as you can see here: Server sent security types, but we do not support any of their. Which digging the log it is: 12:11:18:247 List of security type is read Now the connection from the Windows side is failing ( full log in pastebin) with this error:
I used to connect to my machine form a Windows one using TightVNC and it worked flawlessly till yesterday (). The facts: I had a configuration for sharing my desktop that worked till the recent update of Gnome desktop to use sgnome-shell 3.10.
0 kommentar(er)
