On Tue, Jan 19, 1999, James H.G. Redekop wrote:
> I am having trouble getting mod_ssl to behave for a customer. It
> compiled beautifully and everything, but now that it's up and running
> it is rejecting all attempts at a connection with this error:
>
> [Tue Jan 19 12:57:54 1999] [error] mod_ssl: Unable to configure server
> private key for connection (SSLeay library error follows)
>
> I'm not sure where the SSLeay library error would be found.
Usually directly following this error message. But there
are some cases inside SSLeay where no error message is set.
> I'm running on a SPARC Solaris 2.6 box with certificates from Thawte.
> The certificate key was generated on an Intel Solaris 2.5 box, possibly
> with an earlier version of SSLeay -- could that be the problem? If so,
> is there a way of fixing that short of having to order a whole new
> certificate?
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. I guess
you're problem is already at this stage. Perhaps the server.key is not PEM
encoded, etc.
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]
