- Provides interfaces for generating RSA (Rivest, Shamir and
Adleman AsymmetricCipher algorithm)
keys as defined in the RSA Laboratory Technical Note
PKCS#1, and DSA (Digital Signature
Algorithm) keys as defined in NIST's FIPS-186. more ...

DSAKey | The interface to a DSA public or private key. | code | html |

DSAKeyPairGenerator | An interface to an object capable of generating DSA key pairs. | code | html |

DSAParams | Interface to a DSA-specific set of key parameters, which defines a
DSA key family. |
code | html |

DSAPrivateKey | The standard interface to a DSA private key. | code | html |

DSAPublicKey | The interface to a DSA public key. | code | html |

ECKey | The interface to an elliptic curve (EC) key. | code | html |

ECPrivateKey | The interface to an elliptic curve (EC) private key. | code | html |

ECPublicKey | The interface to an elliptic curve (EC) public key. | code | html |

RSAKey | The interface to an RSA public or private key. | code | html |

RSAMultiPrimePrivateCrtKey | The interface to an RSA multi-prime private key, as defined in the
PKCS#1 v2.1, using the Chinese Remainder Theorem
(CRT) information values. |
code | html |

RSAPrivateCrtKey | The interface to an RSA private key, as defined in the PKCS#1 standard,
using the Chinese Remainder Theorem (CRT) information values. |
code | html |

RSAPrivateKey | The interface to an RSA private key. | code | html |

RSAPublicKey | The interface to an RSA public key. | code | html |

- Provides interfaces for generating RSA (Rivest, Shamir and
Adleman AsymmetricCipher algorithm)
keys as defined in the RSA Laboratory Technical Note
PKCS#1, and DSA (Digital Signature
Algorithm) keys as defined in NIST's FIPS-186.
- PKCS #1: RSA Encryption Standard, Version 1.5, November 1993
- Federal Information Processing Standards Publication (FIPS PUB) 186: Digital Signature Standard (DSS)

Note that these interfaces are intended only for key implementations whose key material is accessible and available. These interfaces are not intended for key implementations whose key material resides in inaccessible, protected storage (such as in a hardware device).

For more developer information on how to use these
interfaces, including information on how to design
`Key`

classes for hardware devices, please refer
to these cryptographic provider developer guides: