Re: Entrust SDK issue
From: Paul Rubin (//phr.cx_at_NOSPAM.invalid)
Date: 12/06/03
- Next message: r.e.s.: "Re: Good enough for crypto?"
- Previous message: Dominic: "Re: cryptohistory (DES...)"
- In reply to: Henrick Hellström: "Re: Entrust SDK issue"
- Next in thread: Randy Howard: "Re: Entrust SDK issue"
- Reply: Randy Howard: "Re: Entrust SDK issue"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 05 Dec 2003 19:52:04 -0800
Henrick Hellström <henrick.hellstrm@telia.com> writes:
> > I don't remember OpenSSL ever being advertised as thread safe.
>
> Neither do I, to be honest, but I work in a programming environment
> where thread safety is considered to be the norm and not the exception.
Actually, Apache 2.0 is multi-threaded and uses OpenSSL, so OpenSSL must
at least attempt to be thread safe. Whether there's bugs, I don't know.
I continue to run Apache 1.3 which is single threaded (pre-forking).
- Next message: r.e.s.: "Re: Good enough for crypto?"
- Previous message: Dominic: "Re: cryptohistory (DES...)"
- In reply to: Henrick Hellström: "Re: Entrust SDK issue"
- Next in thread: Randy Howard: "Re: Entrust SDK issue"
- Reply: Randy Howard: "Re: Entrust SDK issue"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
