From 9d23de58d167ff7d23ee1b8da675ec1b26b885f9 Mon Sep 17 00:00:00 2001 From: Ben Perez Date: Tue, 4 Feb 2025 23:13:16 +0000 Subject: [PATCH] 8184352: Remove Sun provider information from KeyPairGenerator javadoc Reviewed-by: mullan --- .../classes/java/security/KeyPairGenerator.java | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/src/java.base/share/classes/java/security/KeyPairGenerator.java b/src/java.base/share/classes/java/security/KeyPairGenerator.java index 6d7148a76f5..bc10bc92550 100644 --- a/src/java.base/share/classes/java/security/KeyPairGenerator.java +++ b/src/java.base/share/classes/java/security/KeyPairGenerator.java @@ -68,16 +68,9 @@ import sun.security.util.Debug; *

Since no other parameters are specified when you call the above * algorithm-independent {@code initialize} methods, it is up to the * provider what to do about the algorithm-specific parameters (if any) to be - * associated with each of the keys. - * - *

If the algorithm is the DSA algorithm, and the keysize (modulus - * size) is 512, 768, 1024, or 2048, then the Sun provider uses a set of - * precomputed values for the {@code p}, {@code q}, and - * {@code g} parameters. If the modulus size is not one of the above - * values, the Sun provider creates a new set of parameters. Other - * providers might have precomputed parameter sets for more than just the - * modulus sizes mentioned above. Still others might not have a list of - * precomputed parameters at all and instead always create new parameter sets. + * associated with each of the keys. See the + * {@extLink security_guide_jdk_providers JDK Providers} document for information + * on the default algorithm-specific parameters used by JDK providers. * *

  • Algorithm-Specific Initialization *

    For situations where a set of algorithm-specific parameters already