In message <[EMAIL PROTECTED]> on Sat, 21 May 2005 19:11:20 +0200, Corinna
Vinschen <[EMAIL PROTECTED]> said:
vinschen> What about my question:
vinschen>
vinschen> >> What I'm not sure about is, if the engines shouldn't
vinschen> >> better be installed into /usr/bin. Otherwise they are
vinschen> >> only loadable using full paths, or when $PATH also
vinschen> >> contains the engine installation path, according to
vinschen> >> Windows DLL loading rules. I'd be grateful about a hint
vinschen> >> here...
vinschen>
vinschen> Is that something to worry about at all?
The following from CHANGES should explain it:
*) Change the ENGINE framework to automatically load engines
dynamically from specific directories unless they could be
found to already be built in or loaded. Move all the
current engines except for the cryptodev one to a new
directory engines/.
The engines in engines/ are built as shared libraries if
the "shared" options was given to ./Configure or ./config.
Otherwise, they are inserted in libcrypto.a.
/usr/local/ssl/engines is the default directory for dynamic
engines, but that can be overriden at configure time through
the usual use of --prefix and/or --openssldir, and at run
time with the environment variable OPENSSL_ENGINES.
[Geoff Thorpe and Richard Levitte]
Cheers,
Richard
-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.
--
Richard Levitte [EMAIL PROTECTED]
http://richard.levitte.org/
"When I became a man I put away childish things, including
the fear of childishness and the desire to be very grown up."
-- C.S. Lewis
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
