Thanks Ron... I just did this, and there was no change -- it still
doesn't like this directive:
Invalid command 'SSLCryptoDevice', perhaps mis-spelled
or defined by a module not included in the server configuration
My build was effectively:
cd openssl* && sh config -fPIC -DSSL_EXPERIMENTAL shared && make
&& cd ..
cd mm-1.1.3 && ./configure --disable-shared && make && cd ..
cd mod_ssl-2.8.10-1.3.26 && ./configure
--with-apache=../apache_1.3.26 \
--with-ssl=../openssl-engine-0.9.6d \
--with-mm=../mm-1.1.3 \
--enable-rule=SSL_EXPERIMENTAL \
--enable-module=ssl \
--prefix=/usr/local/apache --enable-shared=ssl \
--enable-module=most \
--enable-shared=max --enable-module=so && cd ..
cd apache_1.3.26 && make && make install
package-root=`pwd`/package-root
The difference I am doing is removing the "--enable-shared=ssl" and
"--enable-shared=max", and then it works (as a static).
Thanks,
James
>>> [EMAIL PROTECTED] 06/28/02 01:45pm >>>
It might depend upon how you compliled openssl, was it compiled shared
also?
Thanks,
Ron DuFresne
On Fri, 28 Jun 2002, James Bromberger wrote:
> Hey people.
>
> I have been running fine with Apache + Mod_SSL under Solaris with
> everything working fine. I am now recompiling to Apache 1.3.26,
Mod_SSL
> 2.8.10, OpenSSL 0.9.6d, and MM1.1.3. My httpd.conf is pretty much
the
> default, except for just above the SSLPassPhraseDialog (around line
> 1090) where I have:
> SSLCryptoDevice cswift
>
> (it is a Sun Cyrpto Accelerator 1 (just a rebadged CryptoSwift) in a
> Netra T1, on Solaris 8)
>
>
> There are two compiles I have done: one where I have done everything
as
> a static, and one where it is DSO. When static, I removed my
LoadModules
> and AddModules, and of course, when as a DSO, I add these back in.
ALl
> pretty straight forward.
>
> When I use static, my hardware crypto is working and everything is
> wonderful. Birds sing, etc...
>
> When I go DSO and then `apachectl configtest`:
>
> Invalid command 'SSLCryptoDevice', perhaps mis-spelled
> or defined by a module not included in the server configuration
>
> Which is odd, because all the other SSL directives are OK. If I do a
> `strings libexec/libssl.so` then I can see that the SSLCryptoDevice
is
> mentioned in the module, however using mod_info, it is not mentioned
> against mod_ssl as being available.
>
> Does anyone know what is going on here? Why would this work fine as
a
> static, and not as a DSO? This was working with earlier versions
(1.3.20
> & 2.8.4 & 0.9.6b).
>
> Any help appreciate.
>
> James
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
admin & senior security consultant: sysinfo.com
http://sysinfo.com
"Cutting the space budget really restores my faith in humanity. It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation."
-- Johnny Hart
testing, only testing, and damn good at it too!
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
--
James Bromberger,
Senior Web/Systems Administrator, JDV
+61 8 9268 2909, +61 417 322 500
Fax: +61 8 9266 0200
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
