xref: /freebsd/secure/lib/libcrypto/man/man7/EVP_PKEY-X25519.7 (revision cb2887746f8b9dd4ad6b1e757cdc053a08b25a2e)
-*- mode: troff; coding: utf-8 -*-
Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45)

Standard preamble:
========================================================================
..
..
.. \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
. ds C` "" . ds C' "" 'br\} . ds C` . ds C' 'br\}
Escape single quotes in literal strings from groff's Unicode transform.

If the F register is >0, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.

Avoid warning from groff about undefined register 'F'.
.. .nr rF 0 . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF ========================================================================

Title "EVP_PKEY-X25519 7ossl"
EVP_PKEY-X25519 7ossl 2025-07-01 3.5.1 OpenSSL
For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
NAME
EVP_PKEY-X25519, EVP_PKEY-X448, EVP_PKEY-ED25519, EVP_PKEY-ED448, EVP_KEYMGMT-X25519, EVP_KEYMGMT-X448, EVP_KEYMGMT-ED25519, EVP_KEYMGMT-ED448 \- EVP_PKEY X25519, X448, ED25519 and ED448 keytype and algorithm support
DESCRIPTION
Header "DESCRIPTION" The X25519, X448, ED25519 and ED448 keytypes are implemented in OpenSSL's default and FIPS providers. These implementations support the associated key, containing the public key pub and the private key priv.
"Keygen Parameters"
Subsection "Keygen Parameters"
"""dhkem-ikm"" (OSSL_PKEY_PARAM_DHKEM_IKM) <octet string>" 4
Item """dhkem-ikm"" (OSSL_PKEY_PARAM_DHKEM_IKM) <octet string>" DHKEM requires the generation of a keypair using an input key material (seed). Use this to specify the key material used for generation of the private key. This value should not be reused for other purposes. It should have a length of at least 32 for X25519, and 56 for X448. This is only supported by X25519 and X448.
"""fips-indicator"" (OSSL_PKEY_PARAM_FIPS_APPROVED_INDICATOR) <integer>" 4
Item """fips-indicator"" (OSSL_PKEY_PARAM_FIPS_APPROVED_INDICATOR) <integer>" This getter is only supported by X25519 and X448 for the FIPS provider. Since X25519 and X448 are unapproved in FIPS 140-3 this getter return 0. .Sp See "Common Information Parameters" in provider-keymgmt\|(7) for further information.

Use EVP_PKEY_CTX_set_params() after calling EVP_PKEY_keygen_init().

"Common X25519, X448, ED25519 and ED448 parameters"
Subsection "Common X25519, X448, ED25519 and ED448 parameters" In addition to the common parameters that all keytypes should support (see "Common parameters" in provider-keymgmt\|(7)), the implementation of these keytypes support the following.
"""group"" (OSSL_PKEY_PARAM_GROUP_NAME) <UTF8 string>" 4
Item """group"" (OSSL_PKEY_PARAM_GROUP_NAME) <UTF8 string>" This is only supported by X25519 and X448. The group name must be "x25519" or "x448" respectively for those algorithms. This is only present for consistency with other key exchange algorithms and is typically not needed.
"""pub"" (OSSL_PKEY_PARAM_PUB_KEY) <octet string>" 4
Item """pub"" (OSSL_PKEY_PARAM_PUB_KEY) <octet string>" The public key value.
"""priv"" (OSSL_PKEY_PARAM_PRIV_KEY) <octet string>" 4
Item """priv"" (OSSL_PKEY_PARAM_PRIV_KEY) <octet string>" The private key value.
"""encoded-pub-key"" (OSSL_PKEY_PARAM_ENCODED_PUBLIC_KEY) <octet string>" 4
Item """encoded-pub-key"" (OSSL_PKEY_PARAM_ENCODED_PUBLIC_KEY) <octet string>" Used for getting and setting the encoding of a public key for the X25519 and \fBX448 key types. Public keys are expected be encoded in a format as defined by RFC7748.
"ED25519 and ED448 parameters"
Subsection "ED25519 and ED448 parameters"
"""mandatory-digest"" (OSSL_PKEY_PARAM_MANDATORY_DIGEST) <UTF8 string>" 4
Item """mandatory-digest"" (OSSL_PKEY_PARAM_MANDATORY_DIGEST) <UTF8 string>" The empty string, signifying that no digest may be specified.
"CONFORMING TO"
Header "CONFORMING TO"
"RFC 8032" 4
Item "RFC 8032"

0

"RFC 8410" 4
Item "RFC 8410"

EXAMPLES
Header "EXAMPLES" An EVP_PKEY context can be obtained by calling:

.Vb 2 EVP_PKEY_CTX *pctx = EVP_PKEY_CTX_new_from_name(NULL, "X25519", NULL); \& EVP_PKEY_CTX *pctx = EVP_PKEY_CTX_new_from_name(NULL, "X448", NULL); \& EVP_PKEY_CTX *pctx = EVP_PKEY_CTX_new_from_name(NULL, "ED25519", NULL); \& EVP_PKEY_CTX *pctx = EVP_PKEY_CTX_new_from_name(NULL, "ED448", NULL); .Ve

An X25519 key can be generated like this:

.Vb 1 pkey = EVP_PKEY_Q_keygen(NULL, NULL, "X25519"); .Ve

An X448, ED25519, or ED448 key can be generated likewise.

"SEE ALSO"
Header "SEE ALSO" \fBEVP_KEYMGMT\|(3), EVP_PKEY\|(3), provider-keymgmt\|(7), \fBEVP_KEYEXCH-X25519\|(7), EVP_KEYEXCH-X448\|(7), \fBEVP_SIGNATURE-ED25519\|(7), EVP_SIGNATURE-ED448\|(7)
COPYRIGHT
Header "COPYRIGHT" Copyright 2020-2024 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>.