On Fri, Jun 25, 1999, Roman Maeder wrote:
> I compiled and installed Apache 1.3.6 including mod_ssl-2.3.5-1.3.6 and mod_perl-1.20
> under SunOS 4.1.4 using Procedure 5 b) from the INSTALL file
> ('The flexible APACI-only way [FOR REAL HACKERS]').
>
> The only problem encountered was during the final install of apache
> ('make install'):
> ...
> [PRESERVING EXISTING CERTIFICATE FILES: /export/www/apache/conf/ssl.crt/*]
> Updating hash symlinks in /export/www/apache/conf/ssl.crt/:
> ca-bundle.crt -> [skipped]
> /bin/sh: ssleay: not found
> server.crt -> .0
> ...
>
> why 'ssleay'? I configured mod_ssl-2.3.5-1.3.6 with
> --with-ssl=/usr/local/openssl
> and apache_1.3.6 with
> env SSL_BASE=/usr/local/openssl ./configure ...
> so it should use /usr/local/openssl/bin/openssl, shouldn't it?
Under /export/www/apache/ you already had an installed Apache and you're
upgrading. So _AS APACI CLEARY SAID IN UPPER CASE_ it preserves all files
/export/www/apache/conf/ssl.crt/*, i.e. including the Makefile there. So the
old Makefile is used and there (because of an old version) ssleay is used.
Just rename ssl.crt to ssl.crt.old, do again an install and copy over the
stuff from ssl.crt.old to ssl.crt - except for the Makefile.
> (one minor observation: after configuring mod_ssl with '--with-ssl=...',
> couldn't it stick that information into the Apache configuration,
> so setting the SSL_BASE environment variable would no longer be necessary
> [one fewer source of errors])
You're using the "The flexible APACI-only way [FOR REAL HACKERS]" which means
that all is under _your_ control. When you want automatic SSL_BASE handling
you have to use the JOE AVERAGE variant ;)
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]