Comment 6 for bug 1281250

Sebastian: no. the default is to use encryption. But after updating vino (do not remember at which point), vino changed the security type to a new one (at least, I think); the connection stopped to work with the error reported above and the only solution to have it back was to disable encryption.

What I *suppose* happened is that the vino server upgraded the encryption algorithm and the clients have still to catch up; the problem is that there seems no way to say vino to use an old encryption --- it just works with the "type 18" or none.