On Sun, Mar 22, 2009 at 02:41:44PM +0200, Pasi Kärkkäinen wrote: > On Sun, Mar 22, 2009 at 02:14:35PM +0200, Pasi Kärkkäinen wrote: > > On Tue, Mar 10, 2009 at 01:31:06PM +0100, Pierre Ossman wrote: > > > On Tue, 10 Mar 2009 13:46:12 +0200 > > > Pasi Kärkkäinen <pa...@iki.fi> wrote: > > > > > > > > > > > Hmm.. I'm not really familiar with the UltraVNC design and/or code.. > > > > > > > > http://code.google.com/p/vncthumbnailviewer/source/detail?r=16 > > > > > > > > Quote from that page: > > > > > > > > "It appears that... > > > > > > > > u...@vnc's MS-Logon 1 uses the RFB version string to communicate it's > > > > desire > > > > to use a different authentication technique. If the version is 003.004 > > > > the > > > > Security Negotiation requests it uses VNCAuthentication and does a > > > > hybrid of > > > > VncAuthentication (DES encrypted with a fixed key) and MS Challenge. > > > > > > > > u...@vnc's MS-Logon II uses the Security Negotiation protocol (send > > > > "-6") to > > > > select their MS Logon Authentication procedure." > > > > > > > > Is "MS-Logon II" better, or something that can be supported/added? > > > > Would be nice to have both though. > > > > > > > > > > MS-Logon II would be possible to add. They should register it with > > > RealVNC first though. We should not be using unofficial protocol > > > numbers in a stable release of the software. > > > > > > > I posted to ultravnc forums about this: > > http://forum.ultravnc.info/viewtopic.php?t=14896 > > > > Not much replies.. (at least not yet). > > > > > Then there's the matter of someone actually writing the code for it. > > > Please add it to the feature tracker, as right now it isn't really > > > realistic to fit in the road map (unless someone else does the work). > > > > > > > Ok. I'll submit to feature tracker. > > > > Done: > https://sourceforge.net/tracker/index.php?func=detail&aid=2703103&group_id=254363&atid=1126849 >
Ok, I got reply from UltraVNC developer: http://forum.ultravnc.info/viewtopic.php?t=14896 Quote: "The only published protocol versions at this time are 3.3, 3.7, 3.8 we are using 3.4 and 3.6. The authentication message was added to rfb in 3.7. The message can not be registered unless we move to the new 3.8 rfb. This require more then a simple number update, all new stuff need to be handled. Not possible for now." And then I asked about the 3.4 and 3.6 protocol versions: "Do you know if other VNC implementations are using 3.4 or 3.6 ? Or is it only used in UltraVNC?" reply: "It's only UltraVnc... We actual use 4 and 6 to indicate that FT and/or MS logon is supported and fallback to 3 when viewer isn't able to do them. ( unless ms logon required is checked, then 3.3 fail to connect)" So.. would it be possible to check for protocol versions 3.4/3.6 and then enable UltraVNC specific features in TigerVNC client? -- Pasi ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
