Comment 3 for bug 1281250
Revision history for this message
| Romano Giannetti (romano-giannetti) wrote Re: VNC accessible for Windows machines only with encryption disabled | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
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...