JARs signed with SHA-1 algorithms are now restricted

JARs signed with SHA-1 algorithms are now restricted by default and treated as if they were unsigned in Java SE 17. This applies to the algorithms used to digest, sign, and optionally timestamp the JAR. It also applies to the signature and digest algorithms of the certificates in the certificate chain of the code signer and the Timestamp Authority, and any CRLs or OCSP responses that are used to verify if those certificates have been revoked.

In order to reduce the compatibility risk for applications that have been previously timestamped or use private CAs, there are two exceptions to this policy:

• Any JAR signed with SHA-1 algorithms and timestamped prior to January 01, 2019 will not be restricted.
• Any JAR signed with a SHA-1 certificate that does not chain back to a Root CA included by default in the JDK cacerts keystore will not be restricted.

These exceptions may be removed in a future JDK release.

SHA-1 is no longer considered secure and it should not be used. Users can, at their own risk, remove these restrictions by modifying the java.security configuration file (or overriding it using the java.security.properties system property) and removing SHA1 jdkCA & usage SignedJAR & denyAfter 2019-01-01 from the jdk.certpath.disabledAlgorithms security property and SHA1 jdkCA & denyAfter 2019-01-01 from the jdk.jar.disabledAlgorithms security property.

For more information on this restriction, see Disable SHA-1 Signed JARs.