On Wednesday 16 June 2004 12:46 pm, Richard Levitte - VMS Whacker wrote: > In message <[EMAIL PROTECTED]> on Wed, 16 Jun 2004 > 12:30:28 -0400, Kevin Stefanik <[EMAIL PROTECTED]> said: > > kstef> I think we can make do with a less involved fix, actually, by > kstef> just backing out the conditional if the engine still _requires_ > kstef> its own copy of the libcrypto code, or, preferably, just > kstef> linking to libcrypto dynamically if the earlier requirement no > kstef> longer holds. I just need an expert's best guess and I'll be > kstef> out of your hair. > > Backing out is not an option. The ENGINE_get_static_state() check is > there for a very specific reason that hits most Unixly users, at least > if the engine is linked with the exact dynamic library that loads it. > Since that's a fairly plausible scenario, I think it would be a bad > move not to make any checks of the sort. >
When I try to link the opensc engine to libcrypto (0.9.8) dynamically and then load the engine in openssl, it loads the engine successfully but the UI method to get the pin fails. Is that expected? Kevin ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
