Skip to content

Conversation

@martinuy
Copy link

@martinuy martinuy commented Jun 7, 2022

Search this PR in Red Hat Jira

Diff of this PR only Dependency chain
9087e80...a6e533a rh-openjdk:fipsTHIS PR

A 11u backport of RH1995150 (Disable non-FIPS crypto in SUN and SunEC security providers) is required for a 11u backport of RH2052070 (Enable AlgorithmParameters and AlgorithmParameterGenerator services in FIPS mode).

This backport includes the following 17u RPM patches:

Bugzillas:

Conflicts when applying the 17u RH1995150 to 11u:

franferrax
franferrax previously approved these changes Sep 26, 2022
Copy link

@franferrax franferrax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me:

  • It leaves the same algorithms and services enabled in SunEntries.java / SunEC.java as rh-openjdk/jdk@765baf2
    • Except for putEdDSAEntries() ones, since we don't have JDK-8166597, as explained in the description (we'll have to be vigilant and disable the KeyPairGenerator / KeyAgreement entries if that backport is done)
  • It fixes the same issue as the one fixed in rh-openjdk/jdk@da9988c, by granting the accessClassInPackage runtime permission on the jdk.internal.misc package to the jdk.crypto.ec module (for 17u, the package was jdk.internal.access)

Copy link

@franferrax franferrax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Files modified in this pull request didn't change in the last force-push, the following command gives no output:

git diff 675c3b9582c1e159b09f9cb06d14cceff46f8082 a6e533a37276fefc27f13a342fa43acc9d425f7c -- \
  src/java.base/share/classes/module-info.java                      \
  src/java.base/share/classes/sun/security/provider/SunEntries.java \
  src/java.base/share/lib/security/default.policy                   \
  src/jdk.crypto.ec/share/classes/sun/security/ec/SunEC.java

Also, the Files changed section shows the same files, no new files were added. So the previous review still applies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants