How about the server determines the authentication protocol, so when you setup your server, you say what to use and what domain or server,
then the client just have username/password fields. Richard, I do agree that the code would be a nightmare and it would take someone really good to achieve all of them. ? -----Original Message----- From: richard.harris [mailto:richard.harris@;nottscc.gov.uk] Sent: 31 October 2002 11:30 To: vnc-list Subject: RE: SOE VNC - COOL! > What would it take to get RealVNC to have features like SOE VNC, i.e. the NT > Authentication? > What about other Authentication Realms? We've come back full circle to the plug-in idea haven't we? :-) If VNC was to support different authentication mechanisms, IMO I'd rather have these as options rather than as a standard. Kerberos or LDAP (NDS, openldap, AD) queries might be better in a big network, but could be a nightmare to code for. The other option is what happens when the machine can't see the authentication system, but is still VNCable.... can you still logon? > I think that would be a lot safer than a password based authentication How much work would be required for all viewers to be able to negoiate an authentication method? Have the server report to the client that "the following methods are supported.... " perhaps start with the basic VNC system, then offer local user account (okay for windows, unix - I don't know about macs) Later, Richard --------------------------------- Richard Harris Environment IT, NCC Ext 4509 --------------------------------- "Service, price , quality: pick any two." _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list