At 10:28 AM 11/5/2002 -0500, Oblio writeth:
>I'm not sure what these two files are, either (I think you meant 
>'ssleay32.dll and libeay32.dll').  However, I've found that a number of 
>programs I have installed include versions of them, and there's a copy in 
>my system32 directory.  I can give you a copy if you'd like.
>
>Can anyone else tell us where these come from, and what they do?  (And why 
>the different copies on my system are different sizes?)

They usually come from pre-built sources.  Technically end-users should do
the compilation of OpenSSL for their systems and companies should not
incorporate OpenSSL into their product lines because of import and export
regulations (legal issues just get messy in regards to cryptography
software).  However, many Windows-oriented products include OpenSSL
binaries to make end-users lives easier.  The downside to distributing the
binaries is that every product that uses OpenSSL has to keep OpenSSL
updated - thus requiring additional resources that could be spent doing
something else.  Hence the reason for the Win32 OpenSSL Installation
Project.  It deals with the legal issues of distributing OpenSSL, Windows
programming/development issues, and end-user issues all at the same time in
one convienent package.

The reason for different sizes is usually due to whatever compiler the
company used to build the DLLs.  Also, the OpenSSL DLLs may be different
versions...and anything below v0.9.6f/0.9.6g is subject to several serious
security-oriented issues.

Hope this helps!


          Thomas J. Hruska -- [EMAIL PROTECTED]
Shining Light Productions -- "Meeting the needs of fellow programmers"
                  http://www.shininglightpro.com/
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to