Opening a JAR file triggers, on first use, the loading of a lot of security classes that should only needed when the JAR file is signed.

One issue is SignatureFileVerifier.isBlockOrSF(String) which triggers DisabledAlgorithmConstraints to be loaded and 20+ other classes to be and initialized. This issue is created to change the initialization of DisabledAlgorithmConstraints to be lazy.