On Wed, Mar 10, 1999, glin wrote:
Seems to me, according to the message, the certificate is corrupted or
modified, or signed with a different private key from the ca's. Did you see
this msg in the server's log? Or in the browser?
Hello Probably this question concerns the ssleay's work,
"Ralf S. Engelschall" wrote:
On Wed, Mar 10, 1999, glin wrote:
Seems to me, according to the message, the certificate is corrupted or
modified, or signed with a different private key from the ca's. Did you see
this msg in the server's log? Or in the browser?
Nothing appears in the
On Wed, Mar 10, 1999, glin wrote:
Seems to me, according to the message, the certificate is corrupted or
modified, or signed with a different private key from the ca's. Did you see
this msg in the server's log? Or in the browser?
Nothing appears in the log files but Netscape
On Thu, Mar 11, 1999, Anton Voronin wrote:
On Wed, Mar 10, 1999, glin wrote:
Seems to me, according to the message, the certificate is corrupted or
modified, or signed with a different private key from the ca's. Did you see
this msg in the server's log? Or in the browser?
Hello
Probably this question concerns the ssleay's work, but maybe someone here can
help me...
When the sign.sh script verifies the certificate (ssleay verify -CAfile ca.crt
server.crt), the following error appears:
error 7 at 0 depth lookup:certificate signature failure
What could be wrong
