Ralf S. Engelschall wrote:
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
Ralf S. Engelschall wrote:
It's fine, I tracked things down. The wrong key file had been copied
over to the production server, so it didn't match the crt. Thanks for
the advice in any case!
Oh, that's good news ;-)
Then it was just some sort of a configuration error...
Yes --
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
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
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:
Ralf S. Engelschall wrote:
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 figured as much. Ah well.
Usually it doesn't matter where it was generated,
