![]() This version includes changes from 2022b that merged multiple regions that have the same timestamp data post-1970 into a single time zone data. Users can, at their own risk, remove these restrictions by modifying the curity configuration file (or override it by using the system property) and removing "SHA1 usage SignedJAR & denyAfter " from the security property and "SHA1 denyAfter " from the security property.Ĭore-libs/java.time ➜ Update Timezone Data to 2022c JARs affected by these new restrictions should be replaced or re-signed with stronger algorithms. ![]() =MD2, MD5, RSA keySize < 1024, DSA keySize < 1024, SHA1 denyAfter WARNING: The jar will be treated as unsigned, because it is signed with a weak algorithm that is now disabled by the security property: Signature algorithm: SHA1withRSA (disabled), 2048-bit key To determine if your signed JARs are affected by this change, run jarsigner -verify -verbose -certs on the signed JAR, and look for instances of "SHA1" or "SHA-1" and "disabled" and a warning that the JAR will be treated as unsigned in the output. This exception may be removed in a future JDK release.
0 Comments
Leave a Reply. |