[Openswan dev] Removal of #ifdef X509 code completed

Andreas Steffen andreas.steffen at strongsec.net
Sun Mar 7 12:20:46 CET 2004

Thanks Ken!

Actually I don't understand why you need the #ifdef X509_FETCH
statements at all. If crlcheckinterval is set to 0 seconds
(which is the default setting) then no threads are started,
so there will be no concurrent processing. Just a couple of mutexes
are in place which should do no harm.



Ken Bantoft wrote:
> Hash: SHA1
> I've comitted changes in CVS to remove the #ifdef X509 code.
> #ifdef X509_FETCH is still in place at the moment, as it uses threads, and 
> there is some belief that other parts of Openswan are not currently 
> thread-safe.  Hopefully we can get this resolved shortly.
> Note: I haven't fully tested it, but the regression tests will let me know 
> Sunday morning if I missed anything.
> - -- 
> Ken Bantoft			VP Business Development
> ken at xelerance.com		Xelerance Corporation
> sip://toronto.xelerance.com	http://www.xelerance.com
> The future is here. It's just not evenly distributed yet. 
>         -- William Gibson
> Version: GnuPG v1.2.1 (GNU/Linux)
> iD8DBQFASqfNPiOgilmwgkgRAoJzAKDAVl+fit2+3tqQpvw16oyK4fpAIACeJt1s
> co/is6oM0eMlARTLyFGPwmE=

Andreas Steffen                   e-mail: andreas.steffen at strongsec.com
strongSec GmbH                    home:   http://www.strongsec.com
Alter Zürichweg 20                phone:  +41 1 730 80 64
CH-8952 Schlieren (Switzerland)   fax:    +41 1 730 80 65
==========================================[strong internet security]===

More information about the Dev mailing list