Honestly, I didn't develop those extensions, so I'm trying to process the information second-hand. :) If the same functionality can be implemented without using the Tight security type, then I guess I have no problem with removing it. UCAR ultimately wants to look at implementing the TurboVNC auth extensions in TigerVNC, so they'll be in a better position to figure out what parts of VeNCrypt they can leverage for that. It sounds like the basic functionality is already there-- it just needs a little tweaking on the server end, perhaps.
On 11/8/10 12:47 AM, Martin Koegler wrote: > Tigervnc C client+server support VeNCrypt to advertise new auth > types. I looked at the turbovnc sources: > > * UnixLogin is the same as the Plain security type [maybe a > new/modifed password validator is necessary]. > > * OTP is on the network side the same as VncAuth - so it is something, > that can be implemented by extending the the VncAuth password validation. > > The main question about the importance to advertise capabilities is: > Why has nobody missed this fetature, when using the C client? ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
