{"id":3474,"date":"2017-10-30T20:36:03","date_gmt":"2017-10-30T19:36:03","guid":{"rendered":"https:\/\/monodes.com\/predaelli\/?p=3474"},"modified":"2017-10-30T13:39:18","modified_gmt":"2017-10-30T12:39:18","slug":"gnomes-like-wine-and-vinegar","status":"publish","type":"post","link":"https:\/\/monodes.com\/predaelli\/2017\/10\/30\/gnomes-like-wine-and-vinegar\/","title":{"rendered":"Gnomes like wine and vinegar"},"content":{"rendered":"

<\/a>\"\"<\/a>gnome3 – How can I connect to Gnome 3 with a Windows VNC client? Got “rightly” answered on Unix & Linux Stack Exchange<\/a><\/em><\/p>\n

\n
\n

Here are some other possible solutions:<\/p>\n

    \n
  1. Disable Vino encryption, and then setup an SSH tunnel<\/del><\/li>\n
  2. Use a VNC client compatible with Vino’s TLS version: Android: bVNC Free, Windows: SSVNC, Linux: vinagre<\/strong><\/li>\n
  3. Use a different VNC server, such as tigervnc or x11vnc<\/li>\n
  4. Use a different VNC server, such as tightvnc, with a different desktop manager, such as MATE, Xfce, LXDE, etc.<\/li>\n<\/ol>\n<\/div>\n<\/blockquote>\n

    <\/p>\n

    The first is not a solution, but a user-made security hole, unless you allow only localhost connections to vnc. The real issue is that I wasn’t aware that vinagre supported the TLS encryption used by vino.<\/p>\n

    As usual program names of free-as-in-freedom software are full of puns:<\/p>\n