UltraVNC

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 ...

Based on this: http://code.google.com/p/vncthumbnailviewer/source/detail?r=16

"Ultr@VNC's MS-Logon II uses the Security Negotiation protocol (send "-6") to select their MS Logon Authentication procedure."

It seems the already registered "Ultra" extension (Number 17 in the RFB spec) is not used for ...

I guess it's best to continue the discussion on the other (earlier) thread:
[topic=14896][/topic]

It's easy to ask for protocol numbers.. just send an email. examples here:

http://www.realvnc.com/pipermail/vnc-li ... 59462.html
http://www.realvnc.com/pipermail/vnc-li ... 59611.html

It's easy to ask for protocol numbers.. just send an email. examples here:

http://www.realvnc.com/pipermail/vnc-li ... 59462.html
http://www.realvnc.com/pipermail/vnc-li ... 59611.html

Hello.

I posted to "[MS logon] Bug reports & General help" about this already:
[topic=14896][/topic]

It would be nice if UltraVNC developers registered MS-Logon II protocol number to the 'official' VNC protocol specification.. so other VNC projects could support it too..

http://www.realvnc.com ...

another style of mslogon is available on commercial product of realvnc not free version.

Yeah.. but I just meant to register the MS-Logon II extension/feature, just like all the other extra features are registered in the 'official' vnc protocol documentation maintained by RealVNC.

http://www ...

Hello.

Are UltraVNC developers planning to register MS-Logon II protocol number with RealVNC?

TigerVNC client (and others) can't (or don't want to) add support for that before it's officially registered with RealVNC..