Dear openssl-users:
We have some old certificates that have ill-formed value for the
subjectAltName extension, causing the TLS handshake to fail.
Are there any options that can be configured to by-pass the parsing of the
subjectAltName extension (or all the x509v3 extensions) during TLS
handshake
piry date are blank. So something is probably wrong with the CA cert.
Any help would be much appreciated!
-
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA
--
View this message in context:
Hi,
I've installed the new CA cert on a computer whose clock has been pulled
back. For
a mail signed in the past, Thunderbird says "could not verify this
certificate for
unknown reasons".
However, it can display the certificate chain properly.
-----
--
Kent Tong
Wicket t
:92:
80:3f:20:99:47:1e:3a:0e:48:00:ca:ae:51:54:3b:90:51:54:
52:b9:7d:7c:75:6d:99:9e:73:27:50:1a:f2:eb:2f:4d:cd:8a:
5e:a8:1d:10:d2:42:7c:b7:ac:95:b8:47:55:f9:82:c8:17:61:
5f:f6
-
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/E
rtificate".
Is this the normal behavior or I did not renew the CA cert properly?
I did notice that the new CA cert uses sha1WithRSAEncryption as the
signature
algorithm while the old one uses md5WithRSAEncryption. Is this the problem?
If so, how to correct it?
Thanks!
-
--
Kent Tong
Wic
Hi all,
I have generated a cert request with OpenSSL and
sent it to the CA, now I get back the development certs from them.
Unfortunately, I don't know how to use OpenSSL to sign our applications, which
are Java Applets. Also, what need to concern to deploy the signed applications.
Many
