I thought I had fixed that problem, but hadn't. This part of the code
is currently only used by the ENGINE part, but is also available to
anyone who wants to use it.
Also, a quick fix showed that other problems pop up when you do enable
DSO by default on Win32. At least there was a problem testing the
ENGINE part with CryptoSwift (The instruction at "0x0012f9d0"
reference memory at "0x00000002". The memory couldn't be "written"),
and I currently have no clue if this is a problem in DSO or if it's in
hw_cswift.c.
This could be treated in two ways:
1) We produce the release as scheduled and simply declare that there
are problems with the ENGINE part on Win32. A fix for this
problem could/should be produced shortly after.
2) We call this a showstopper and push the release for a day or two.
I'm personally in favor of alternative 1, because I'm fairly sure this
is a problem in hw_cswift.c, and the engine distribution is said to be
experimental.
Comments?
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
