On Mon, Nov 02, 1998, George Adams wrote:
> I'm having difficulty getting mod_ssl working with Apache 1.3.3 on my
> machine (Digital Unix 4.0d)
>
> I've followed the instructions in mod_ssl's INSTALL file, using
> SSLeay-0.9.0b and rsaref-2.0 . Once everything was built, I tried doing a
> "make certifcate TYPE=test", which crashed with the message:
>
> Generating RSA private key, 1024 bit long modulus
> ............./support/mkcert.sh: 22846 Memory fault
> [...]
I'm sure you ignored or overlooked the NOTEs in the INSTALL file and
configured SSLeay with "perl Configure gcc" instead of "perl Configure
alpha-gcc", although your Digital box is Alpha-based, right? Then this is the
root of all your problems. Please re-configure, re-build and re-install SSLeay
and try again.
> Ignoring that problem for a moment, I dig a "make certificate TYPE=dummy",
> which apparently worked.
Sure, TYPE=dummy uses the pre-generated SnakeOil cert/key pair.
> Then I installed and tried out the server in
> HTTP-only and SSL-enabled mode.
>
> I should say here that the only thing unusual about my setup is that, since
> I'm not root, my HTTP server runs on port 4242 and SSL on port 8443. All
> SSL-related entries in httpd.conf are the defaults. ("Listen" is listening
> for the correct ports)
That's all ok.
> HTTP mode (http://mymachine.foo.com:4242) works fine both in http-only and
> ssl-enabled mode. However, when I run "apache startssl", then try to hit
> "https://mymachine.foo.com:8443", Netscape reports that it's waiting for a
> reply and sits there forever.
>
> When I try "s_client -host localhost -port 8443" in SSLeay, I get:
>
> CONNECTED(00000003)
> depth=0 /C=XY/ST=Snake Desert/L=Snake Town/O=Snake Oil, Ltd/OU=Certificate
>Authority/CN=Snake Oil [EMAIL PROTECTED]
> verify error:num=18:self signed certificate
> verify return:1
>
> then SSLeay also hangs, until I kill it.
>
> No error messages are generated in Apache's "access" or "error" logfiles.
>
> Thanks to anyone who can help sort this problem out. Figuring out what's
> causing the "make certificate TYPE=test" memory problem would be good, but
> right now I'm more interested in getting the thing working in ANY form, if
> only with the dummy certificate. If I've left out any critical pieces of
> information, let me know.
Well, I'm now still the opinion that those hangs are just late results of the
real problem: an incorrectly built SSLeay. So please try to re-built SSLeay
with the correct platform string. Run "perl Configure" without arguments for
the actual list of supported platform strings.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
