I agree that the best possible solution would be for the Windows clients (at least TigerVNC and TightVNC) to catch up. Unfortunately this has not happened; for the time being it would be much better if vino could offer the option to go back to the previous Security Type when the client does not support the new one.
The only solution now is disable the encryption completely; I resorted to a loop back ssh connection so that there is no clear traffic on the wifi, but I still need to do the local step with vino in clear way --- almost safe for me because I do not have other local users, but you never know... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281250 Title: VNC accessible for Windows machines only with encryption disabled To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
