As you can see below, this bug is for real (unless I've done something
stupid - please check the record below!). Please tell me if I can
help in some way (it is not a big problem, I just thought it might
confuse people with no experience of NT).
Here's a record of my session (can't cut n paste from NT terminal
windows, so excuse typos as I'm typing a copy myself!). comments in
[...]
tar -xvf <archive for 0.9.4> [this within a bash shell, but following
within MSDOS]
cd openssl-0.9.4
perl Configure VC-WIN32 no-asm no-rsa no-idea
[the output from this looked like you'd expect - in particular, it did
include -DNO_ASM -DNO_RSA and -DNO_IDEA in CFLAG and perl\util\mkdef.pl
was run (with no args other than 32) to create the def files]
ms\do_ms
[the following was in a shell rather than within VC - I source
VCVARS32.BAT on startup, so the shell has the correct environment]
nmake -f ms\ntdll.mak
[long pause for build, with no errors I noticed]
***[error LNK2001: unresolved external symbol for a pile of routines -
see diff later]
[but I saved the version I made earlier :-) with those deleted]
copy ..\libeay32.def ms\
nmake -f ms\ntdll.mak
[link now OK - builds libeay32.dll]
[more compilation]
***[same link errors, now for ssleay32]
copy ..\ssleay32.def ms\
nmake -f ms\ntdll.mak
[success!]
[well, I assume it's success - the tests fail immediately because they
start with RSA ;-]
diffs for the two def files follow:
libeay32.def:
400a401,402
> EVP_OpenFinal @277
> EVP_OpenInit @278
417a420,421
> EVP_SealFinal @287
> EVP_SealInit @288
536a541,543
> PEM_SealFinal @371
> PEM_SealInit @372
> PEM_SealUpdate @373
555a563,564
> PEM_read_RSAPrivateKey @390
> PEM_read_RSAPublicKey @947
567a577,578
> PEM_read_bio_RSAPrivateKey @400
> PEM_read_bio_RSAPublicKey @943
580a592,593
> PEM_write_RSAPrivateKey @410
> PEM_write_RSAPublicKey @949
593a607,608
> PEM_write_bio_RSAPrivateKey @420
> PEM_write_bio_RSAPublicKey @944
728a744,746
> RSAPrivateKey_asn1_meth @480
> RSAPrivateKey_dup @481
> RSAPublicKey_dup @482
1083a1102,1105
> d2i_RSAPrivateKey_bio @751
> d2i_RSAPrivateKey_fp @752
> d2i_RSAPublicKey_bio @945
> d2i_RSAPublicKey_fp @952
1240a1263,1266
> i2d_RSAPrivateKey_bio @854
> i2d_RSAPrivateKey_fp @855
> i2d_RSAPublicKey_bio @946
> i2d_RSAPublicKey_fp @954
ssleay32.def:
52a53
> SSL_CTX_set_tmp_rsa_callback @177
57a59,61
> SSL_CTX_use_RSAPrivateKey @25
> SSL_CTX_use_RSAPrivateKey_ASN1 @26
> SSL_CTX_use_RSAPrivateKey_file @27
145a150
> SSL_set_tmp_rsa_callback @186
156a162,164
> SSL_use_RSAPrivateKey @102
> SSL_use_RSAPrivateKey_ASN1 @103
> SSL_use_RSAPrivateKey_file @104
162a171,176
> SSLv23_client_method @110
> SSLv23_method @111
> SSLv23_server_method @112
> SSLv2_client_method @113
> SSLv2_method @114
> SSLv2_server_method @115
Cheers,
Andrew
Ulf Möller wrote:
>
> On Thu, Dec 09, 1999 at 06:10:51PM +0000, Andrew Cooke wrote:
>
> > - Ichange NSTALL.W32 to mention this. Something like "If you use any of
> > the -no-XXX options in Configure to exclude ciphers you will have to
> > remove entries from libeay32.def and ssleay32.def in the ms directory
> > before link will work.
>
> INSTALL.W32 tells you to run Configure first, and ms\do_ms (or one of
> the other scripts) after that. If you do that, the definition files
> don't contain the excluded ciphers, right?
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
