On Tue, Jan 19, 1999, James H.G. Redekop wrote:
>[...]
> > Usually it doesn't matter where it was generated, because the format
> > and encoding is standardized. What you should do is to run the
> > commands
> >
> > $ ssleay x509 -noout -text -in server.crt
> > $ ssleay rsa -noout -text -in server.key
> >
> > and make sure that both print reasonable things and don't complain.
>
> They *seem* sane enough -- no complaints, no errors, lots of
> two-digit binary numbers seperated by colons (in case you hadn't
> guessed, I'm not particularily encryption-literate...)
>
> > I guess you're problem is already at this stage. Perhaps the
> > server.key is not PEM encoded, etc.
>
> How could I tell, or should the above have told me? Is there a way
> of getting more detailed logging?
No, when the above two commands didn't complain the server.crt and server.key
are at least in correct format. Then, as you already mentioned yourself in
another reply, you should check the file permissions. Perhaps the files are
not readable for the user who starts Apache? OTOH they are read at startup
time, and your error occurs when the key is configured under run-time. So file
permissions shouldn't be your problem. Hmmmm....
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]
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
