out of curiosity, why do you need msvcrtd.dll. This is a debugging library.
As far as I know, you shouldn't need it in a release version. the same
applies to msvcirtd.dll.
> -----Original Message-----
> From: Eugene Levy [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, May 08, 2000 6:20 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Adding BF to tls & WIN32 static linking of ssl libraries.
>
> Is there anyway to add the BF (BlowFish) symmetric cipher to TLS, so
> that within a TLS session, randomly generated BF keys are used? For
> those paranoid with security, a "BF-SHA1" cipher, with 256-448 bit
> random keys can be used. The current release of openssl-0.95a doesn't
> seem to have a TLS cipher with BF, and looking at previous postings,
> many others want this also. Does openssl provide an API for adding
> new TLS ciphers, like it does for adding new X509v3 extensions?
>
> Also, on the WIN32 platform, is it possible to staticly compile and
> link the openssl libraries, so that "ssleay32.dll" & "libeay32.dll"
> files don't need to be distributed with the WIN32 binaries? On the
> Unix side I distribute my SSL app as one standalone binary files,
> but on WIN32 I have to distribute that same app as a binary file,
> plus 4 DLL files: "libeay32.dll", "ssleay32.dll", "msvcirtd.dll", &
> "msvcrtd.dll".
>
> Thank you in advance.
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> Development Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
