Registering UltraVNC MS-Logon II protocol number

[pasik]

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

[redge]

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

[pasik]

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.realvnc.com/docs/rfbproto.pdf

It already seems to contain 'Ultra' authentication extension.. can MS-Logon II be implemented using that extension, or should it be different/separate extension?

[redge]

no idea

[pasik]

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

[pasik]

Based on this: http://code.google.com/p/vncthumbnailvi ... etail?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 MS-Logon II (-6).

Comments?

[Rudi De Vos]

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.

[pasik]

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.

OK. Understood.

Do you know if other VNC implementations are using 3.4 or 3.6 ? Or is it only used in UltraVNC?

[Rudi De Vos]

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)