java.lang.Objectjava.security.KeyPairGeneratorSpi
java.security.KeyPairGenerator
Direct Known Subclasses:
Delegate, DummyKeyPairGenerator
getInstance
factory methods (static methods that
return instances of a given class).
A Key pair generator for a particular algorithm creates a public/private key pair that can be used with this algorithm. It also associates algorithm-specific parameters with each of the generated keys.
There are two ways to generate a key pair: in an algorithm-independent manner, and in an algorithm-specific manner. The only difference between the two is the initialization of the object:
All key pair generators share the concepts of a keysize and a
source of randomness. The keysize is interpreted differently for different
algorithms (e.g., in the case of the DSA algorithm, the keysize
corresponds to the length of the modulus).
There is an
initialize
method in this KeyPairGenerator class that takes these two universally
shared types of arguments. There is also one that takes just a
keysize
argument, and uses the SecureRandom
implementation of the highest-priority installed provider as the source
of randomness. (If none of the installed providers supply an implementation
of SecureRandom
, a system-provided source of randomness is
used.)
Since no other parameters are specified when you call the above
algorithm-independent 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, or 1024, then the Sun provider uses a set of
precomputed values for the p
, q
, and
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
three modulus sizes mentioned above. Still others might not have a list of
precomputed parameters at all and instead always create new parameter sets.
For situations where a set of algorithm-specific parameters already
exists (e.g., so-called community parameters in DSA), there are two
initialize methods that have an AlgorithmParameterSpec
argument. One also has a SecureRandom
argument, while the
the other uses the SecureRandom
implementation of the highest-priority installed provider as the source
of randomness. (If none of the installed providers supply an implementation
of SecureRandom
, a system-provided source of randomness is
used.)
In case the client does not explicitly initialize the KeyPairGenerator
(via a call to an initialize
method), each provider must
supply (and document) a default initialization.
For example, the Sun provider uses a default modulus size (keysize)
of 1024 bits.
Note that this class is abstract and extends from
KeyPairGeneratorSpi
for historical reasons.
Application developers should only take notice of the methods defined in
this KeyPairGenerator
class; all the methods in
the superclass are intended for cryptographic service providers who wish to
supply their own implementations of key pair generators.
Every implementation of the Java platform is required to support the
following standard KeyPairGenerator
algorithms and keysizes in
parentheses:
Benjamin
- RenaudField Summary | ||
---|---|---|
Provider | provider |
Constructor: |
---|
|
Method from java.security.KeyPairGenerator Summary: |
---|
disableFailover, genKeyPair, generateKeyPair, getAlgorithm, getInstance, getInstance, getInstance, getProvider, initialize, initialize, initialize, initialize |
Methods from java.security.KeyPairGeneratorSpi: |
---|
generateKeyPair, initialize, initialize |
Methods from java.lang.Object: |
---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Method from java.security.KeyPairGenerator Detail: |
---|
|
If this KeyPairGenerator has not been initialized explicitly, provider-specific defaults will be used for the size and other (algorithm-specific) values of the generated keys. This will generate a new key pair every time it is called. This method is functionally equivalent to generateKeyPair . |
If this KeyPairGenerator has not been initialized explicitly, provider-specific defaults will be used for the size and other (algorithm-specific) values of the generated keys. This will generate a new key pair every time it is called. This method is functionally equivalent to genKeyPair . |
|
This method traverses the list of registered security Providers, starting with the most preferred Provider. A new KeyPairGenerator object encapsulating the KeyPairGeneratorSpi implementation from the first Provider that supports the specified algorithm is returned. Note that the list of registered providers may be retrieved via the Security.getProviders() method. |
A new KeyPairGenerator object encapsulating the KeyPairGeneratorSpi implementation from the specified provider is returned. The specified provider must be registered in the security provider list. Note that the list of registered providers may be retrieved via the Security.getProviders() method. |
A new KeyPairGenerator object encapsulating the KeyPairGeneratorSpi implementation from the specified Provider object is returned. Note that the specified Provider object does not have to be registered in the provider list. |
|
SecureRandom
implementation of the highest-priority installed provider as the source
of randomness.
(If none of the installed providers supply an implementation of
SecureRandom , a system-provided source of randomness is
used.) |
SecureRandom
implementation of the highest-priority installed provider as the source
of randomness.
(If none of the installed providers supply an implementation of
SecureRandom , a system-provided source of randomness is
used.).
This concrete method has been added to this previously-defined
abstract class.
This method calls the KeyPairGeneratorSpi
initialize method,
passing it |
|
This concrete method has been added to this previously-defined
abstract class.
This method calls the KeyPairGeneratorSpi initialize method,
passing it |