Martin, All you need to do is modify your existing patches such that instead of trying to use the next eight security types, they will use precisely one security type, that we'll allocate to it. If a viewer sees this security type, it selects it and then tells the server which of your custom security mechanisms to use, before re-running the security-type selection stage to select an *actual* security type to use.
Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Martin Kvgler > Sent: 31 January 2006 21:45 > To: James Weatherall > Cc: [email protected] > Subject: Re: session encryption > > On Tue, Jan 31, 2006 at 12:47:52PM -0000, James Weatherall wrote: > > Have you fixed your patches as per our previous discussion > regarding use of > > a security type to introduce custom authentication methods? > > No, I have not found time to do it yet and I am not sure, how > I will do it. > > The solution, that I favour, is to create a chooser security > type, which does basically > the same as processSecurityTypesMsg(), but uses a bigger name > space (eg. 4 byte) and supports Client > side preferences. My other security types will get number > beyond 256 and will be registered only > in the chooser. > > mfg Martin Kvgler > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
