NAME<\/a> Ed25519, Ed448 \u2212 EVP_PKEY Ed25519 and Ed448 support<\/p>\n The Ed25519<\/b> and Ed448<\/b> EVP_PKEY<\/small> implementation supports key generation, one-shot digest sign and digest verify using PureEdDSA and Ed25519<\/b> or Ed448<\/b> (see RFC8032<\/small> ). It has associated private and public key formats compatible with RFC 8410.<\/small><\/p>\n No additional parameters can be set during key generation, one-shot signing or verification. In particular, because PureEdDSA is used, a digest must NOT<\/small><\/b> be specified when signing or verifying.<\/p>\n The PureEdDSA algorithm does not support the streaming mechanism of other signature algorithms using, for example, EVP_DigestUpdate()<\/b>. The message to sign or verify must be passed using the one-shot EVP_DigestSign()<\/b> and EVP_DigestVerify()<\/b> functions.<\/p>\n When calling EVP_DigestSignInit()<\/b> or EVP_DigestVerifyInit()<\/b>, the digest type<\/b> parameter MUST<\/small><\/b> be set to NULL<\/small><\/b> .<\/p>\n Applications wishing to sign certificates (or other structures such as CRLs or certificate requests) using Ed25519 or Ed448 can either use X509_sign()<\/b> or X509_sign_ctx()<\/b> in the usual way.<\/p>\n A context for the Ed25519<\/b> algorithm can be obtained by calling:<\/p>\n EVP_PKEY_CTX *pctx = EVP_PKEY_CTX_new_id(EVP_PKEY_ED25519, NULL);<\/p>\n For the Ed448<\/b> algorithm a context can be obtained by calling:<\/p>\n EVP_PKEY_CTX *pctx = EVP_PKEY_CTX_new_id(EVP_PKEY_ED448, NULL);<\/p>\n Ed25519 or Ed448 private keys can be set directly using EVP_PKEY_new_raw_private_key<\/b>(3) or loaded from a PKCS#8 private key file using PEM_read_bio_PrivateKey<\/b>(3) (or similar function). Completely new keys can also be generated (see the example below). Setting a private key also sets the associated public key.<\/p>\n Ed25519 or Ed448 public keys can be set directly using EVP_PKEY_new_raw_public_key<\/b>(3) or loaded from a SubjectPublicKeyInfo structure in a PEM<\/small> file using PEM_read_bio_PUBKEY<\/b>(3) (or similar function).<\/p>\n Ed25519 and Ed448 can be tested within speed<\/b>(1) application since version 1.1.1. Valid algorithm names are ed25519<\/b>, ed448<\/b> and eddsa<\/b>. If eddsa<\/b> is specified, then both Ed25519 and Ed448 are benchmarked.<\/p>\n This example generates an ED25519<\/small><\/b> private key and writes it to standard output in PEM<\/small> format:<\/p>\n #include
DESCRIPTION<\/a>
NOTES<\/a>
EXAMPLES<\/a>
SEE ALSO<\/a>
COPYRIGHT<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
NOTES <\/a> <\/h2>\n
EXAMPLES <\/a> <\/h2>\n
#include
…
EVP_PKEY *pkey = NULL;
EVP_PKEY_CTX *pctx = EVP_PKEY_CTX_new_id(EVP_PKEY_ED25519, NULL);
EVP_PKEY_keygen_init(pctx);
EVP_PKEY_keygen(pctx, &pkey);
EVP_PKEY_CTX_free(pctx);
PEM_write_PrivateKey(stdout, pkey, NULL, NULL, 0, NULL, NULL);<\/p>\nSEE ALSO <\/a> <\/h2>\n