Harald... We build our software token with -Bsymbolic. In fact all the 
shared objects we create are with -Bsymbolic.   Because of licensing 
issues I can't staticaly bind with libcrypto (and even under debug 
scenarios, it turns out that binding static to libcrypto.a the problem 
occurs as well so this does not fix)....

If you are going to over ride SHA1_Update, you had better override all 
the SHA1_* functions...

Harald Koch wrote:

>>Here is a patch I created for the Makefile.org file to correct the 
>>problem we were having...
>>
> 
> I wouldn't like to see this in OpenSSL by default; there are times when
> you *want* to over-ride functions inside the library in your own
> program, and times when you don't.
> 
> I'd advise you instead to build your software token with -Bsymbolic and
> link it against the static versions of libssl and/or libcrypto. That's
> what we do for our Apache and iPlanet plugins, and it works on most
> UNIXes (I'm currently having trouble with HP/UX, but doesn't everyone? :-)
> 
> 


-- 
Steven A. Bade
UNIX Network Security Cryptographic Strategy and Development Architecture
[EMAIL PROTECTED]
T/L 678-4799
(512)-838-4799

--
To convert from Hogsheads to Cubic Feet - Multiply by 8.4219

"Two-way communication is necessary to proactively facilitate acceptance
and involvement and to get insights about the journey it takes to get where
we want"

this mess is so big and so bad and so tall,
we cannot clean it up, there is no way at all
(Cat in the Hat)



______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to