This applies to the algorithms used to digest, sign, and optionally timestamp the JAR. JARs signed with SHA-1 algorithms are now restricted by default and treated as if they were unsigned. Security-libs/curity ➜ Disable SHA-1 JARs For authorized use only", OU=Class 3 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=USĭistinguished Name: CN=Thawte Timestamping CA, OU=Thawte Certification, O=Thawte, L=Durbanville, ST=Western Cape, C=ZA For authorized use only", OU=Class 2 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=USĭistinguished Name: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=USĭistinguished Name: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. The following root certificates with weak 1024-bit RSA public keys have been removed from the cacerts keystore: + alias name "thawtepremiumserverca "ĭistinguished Name: CN=Thawte Premium Server CA, OU=Certification Services Division, O=Thawte Consulting cc, L=Cape Town, ST=Western Cape, C=ZAĭistinguished Name: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. Security-libs/curity ➜ Removed Root Certificates with 1024-bit Keys
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |