"Moyle, Ed (PCA)" wrote:
>
> Well, the problem is that I am compiling on WinNT using msvc (I know, I
> know... they make me.) Since it's NT, I can't do any symbolic linking...
> Plus, I work on a product that uses a directory structure and build options
> that I don't get to change very easily (the build group can't handle too
> many changes at once). Any "vendor" (openSSL in this case) incs have to be
> in a directory that is a peer of the code I am writing. Making it #include
> <openssl/xyz.h> forces me to either change them all back to the way they
> used to be (i.e. witout the "openssl/", go back to SSLeay0.9.0.b, or spend
> 6-8 weeks of writing supporting documentation to petition the powers that be
> to change "the way it is" so that I can get the changes made to use OpenSSL
> (try justifying this to somebody who doesn't know anything about it).
Hmmm. How much control do you have over the build environment? Could you
for example change the INCLUDE environment variable to add the openssl
include directory?
There are all manner of bug fixes some of which are for some fairly
serious security issues. Using anything other than 0.9.5a is not
advisable.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
