In https://docs.oracle.com/en/java/javase/25/docs/specs/man/jlink.html#jlink-examples, the command `jlink --suggest-providers java.security.Provider` produces the wrong output:
Suggested providers:
java.naming provides java.security.Provider used by java.base
java.security.jgss provides java.security.Provider used by java.base
java.security.sasl provides java.security.Provider used by java.base
java.smartcardio provides java.security.Provider used by java.base
java.xml.crypto provides java.security.Provider used by java.base
jdk.crypto.cryptoki provides java.security.Provider used by java.base
jdk.crypto.ec provides java.security.Provider used by java.base
jdk.crypto.mscapi provides java.security.Provider used by java.base
jdk.security.jgss provides java.security.Provider used by java.base
As of JDK 22, SunEC crypto provider was moved into `java.base` module.
https://bugs.openjdk.org/browse/JDK-8308398
https://bugs.openjdk.org/browse/JDK-8312267
So running `jlink --suggest-providers java.security.Provider` (with let's say `jlink` from JDK 25) produces:
Suggested providers:
java.naming provides java.security.Provider used by java.base
java.security.jgss provides java.security.Provider used by java.base
java.security.sasl provides java.security.Provider used by java.base
java.smartcardio provides java.security.Provider used by java.base
java.xml.crypto provides java.security.Provider used by java.base
jdk.crypto.cryptoki provides java.security.Provider used by java.base
jdk.security.jgss provides java.security.Provider used by java.base
Suggested providers:
java.naming provides java.security.Provider used by java.base
java.security.jgss provides java.security.Provider used by java.base
java.security.sasl provides java.security.Provider used by java.base
java.smartcardio provides java.security.Provider used by java.base
java.xml.crypto provides java.security.Provider used by java.base
jdk.crypto.cryptoki provides java.security.Provider used by java.base
jdk.crypto.ec provides java.security.Provider used by java.base
jdk.crypto.mscapi provides java.security.Provider used by java.base
jdk.security.jgss provides java.security.Provider used by java.base
As of JDK 22, SunEC crypto provider was moved into `java.base` module.
https://bugs.openjdk.org/browse/JDK-8308398
https://bugs.openjdk.org/browse/JDK-8312267
So running `jlink --suggest-providers java.security.Provider` (with let's say `jlink` from JDK 25) produces:
Suggested providers:
java.naming provides java.security.Provider used by java.base
java.security.jgss provides java.security.Provider used by java.base
java.security.sasl provides java.security.Provider used by java.base
java.smartcardio provides java.security.Provider used by java.base
java.xml.crypto provides java.security.Provider used by java.base
jdk.crypto.cryptoki provides java.security.Provider used by java.base
jdk.security.jgss provides java.security.Provider used by java.base
- links to
-
Commit(master)
openjdk/jdk/d55e1b4a
-
Review(master)
openjdk/jdk/27893