-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bouncycastle FIPs leaving a SecureRandom in heap #15889
Comments
@galderz thanks Galder, I'll start next week. |
@sberyozkin It should be reproducible with Graal VM 21.1.0-dev snapshots from here too: https://github.com/graalvm/graalvm-ce-dev-builds/releases/tag/21.1.0-dev-20210325_0249 |
|
Related to #14904. One of the failures is related to
quarkus-integration-test-bouncycastle-fips
module:The issue arises from
org.bouncycastle.crypto.general.Utils
which containsstatic final SecureRandom testRandom = new SecureRandom();
. This class is initialized at build time through:The issue can be solved with a substitution like this. It bypasses the internal check to validation step of generated key/value pairs:
Another option would be for
org.bouncycastle.crypto.general.AES
and other related classes be runtime initialized. Quarkus experts should provide some input on this possibility.The text was updated successfully, but these errors were encountered: