Ensure static fields set during signed jar process #763
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When loading a signed jar file that is on the classpath, such as the
bouncy castle signed JCE jar file, it has been observed that the value
of
jarVerificationProviders
is set to null. This causes aNullPointerException during the loading process.
This update moves the static declaration of
jarVerificationProviders
to be prior to the method call
RestrictedSecurity.checkHashValues()
since this method call needs the value of the field
jarVerificationProviders
to be initialized in order to work correctly.Signed-off-by: Jason Katonica katonica@us.ibm.com