I am working with 0.9.0b under Microsoft C++ 6.1
on Windows NT 4.0 I am running Microsoft IIS as
the web server on my local machine and I have
a test certificate from Verisign.
I am a commercial software developer so I am 
trying to "avoid any emperial entanglements."

I took the "CLI.CPP" client program out of the
"Demos\SSL" directory of the SSLeay release
tree and modified it to compile under windows.

I use this line to configure the SSL system:
  ctx = SSL_CTX_new (SSLv3_method());
in hopes of avoiding any RSA requirements.

When I configure the SSLeay library as:
(Which includes the RSA stuff)

perl util\mk1mf.pl no-asm VC-WIN32 dll

and link the "CLI.CPP" program against the
resulting libeay32.dll and ssleay32.dll libraries
it works great.  It seems to prefer the "RC4-MD5"
cipher.

When I configure the SSLeay library as:
(Both of which nix the RSA stuff)

perl util\mk1mf.pl no-asm no-rsa VC-WIN32 dll
or
perl util\mk1mf.pl no-asm no-patents VC-WIN32 dll

and link the "CLI.CPP" program against the
resulting libraries the program indicates that
it is using cipher "(NONE)" and blows up
later on an SSL_write.  The crash is because
there is no cipher.

MY QUESTIONS:
1) Is there any way to use this library without
having the RSA code in there?

2) What are the "RSAglue" and "RSAref" libraries
and can they help me untangle from having any
patented code in my libraries.

Any help would be appreciated and if you are
ever in Atlanta, GA, USA I would be happy to
buy a beer for anyone that can (and does)
help me with this.

Jon Bennett
[EMAIL PROTECTED]
(770) 956-7873 X 3104
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to