VNC and OpenSSL (long)

[Habermann, David (DA)]

Thanks for the OpenSSL implementation.  I was successful in recompiling and
implementing your work this morning in less than 1 hour (would have taken
less time if I had read your e-mail completely first. :<)  My WinVNC.log
file does indicate that an SSL connection is being made (although I have not
independently confirmed this).  I was amazed at how easy you made this for
us.  Just FYI: I did see one new additional link warning that I don't
believe I saw before:

Linking...
LINK : warning LNK4098: defaultlib "LIBCMT" conflicts with use of other
libs; use /NODEFAULTLIB:library

I like your ideas regarding the PAM-infrastructure authentication system.
I've been wanting to authenticate against NT for quite some time, but my
options have been limited.

I'm not sure why the server-initiated connection would require a client-side
certificate (probably just my ignorance) since I believe all the server does
is open the IP connection.  The client actually still sends the first text
in the negotiation process, so it would still be responsible for asking for
the SSL connection and negotiating ciphers, etc.

Thanks again, and keep up the fine work!

Dave Habermann

-----Original Message-----
From: Joe Ammann [mailto:joe "at" pyx.ch]
Sent: 21 December, 1999 12:20 PM
To: vnc-list "at" uk.research.att.com
Subject: VNC and OpenSSL (long)

Hi all

I finally came round to polish the integration of OpenSSL into VNC. It
builds now cleanly enough so that somebody might want to have a look
into it.

---------------------------------------------------------------------
The VNC mailing list - see http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------