Upstream comment "I guess that the problem occurs after the default was changed to require encryption:
https://git.gnome.org/browse/vino/commit/?id=f37ca213fda500ea2f93d005e945644c2f2e5721 For whatever reason, that fails with some clients. If you want Vino to work with those clients new authentication types need to be added. There is some information about the protocol and security types at: http://sourceforge.net/p/tigervnc/code/HEAD/tree/rfbproto/rfbproto.rst I will not have time to add the security types in the near future." ** Changed in: vino Remote watch: Red Hat Bugzilla #981984 => GNOME Bug Tracker #728267 ** Also affects: vino (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=981984 Importance: Unknown Status: Unknown -- 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
