On Wed, Mar 25, 2009 at 04:40:23PM +0100, Pierre Ossman wrote: > On Tue, 24 Mar 2009 16:25:53 +0200 > Pasi Kärkkäinen <pa...@iki.fi> wrote: > > > > > So.. would it be possible to check for protocol versions 3.4/3.6 and then > > enable UltraVNC specific features in TigerVNC client? > > > > As those versions are not officially allocated to UltraVNC, I'd say no. > There might be a low risk of conflict, but we want to stick to the > proper ways of extending the protocol. >
OK. Understood. > Once UltraVNC is up to date with the current protocol, we can revisit > the issue under a more proper authentication handshake method. > How about adding --enable-uvnc-mslogon-auth (or something) cmdline option to tigervnc client? Default behaviour would not be changed, but when that option is specified, then the non-standard handshake could be used? I've been missing *nix VNC client with out-of-the-box UltraVNC authentication support for years :) (and I can see now why it hasn't been implemented..) -- Pasi ------------------------------------------------------------------------------ _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
