2020-04-15 01:06:12 +08:00
|
|
|
=pod
|
|
|
|
|
|
|
|
=head1 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
|
|
|
|
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
|
|
|
|
The B<X25519>, B<X448>, B<ED25519> and B<ED448> keytypes are
|
2020-04-20 15:22:41 +08:00
|
|
|
implemented in OpenSSL's default and FIPS providers. These implementations
|
|
|
|
support the associated key, containing the public key I<pub> and the
|
|
|
|
private key I<priv>.
|
|
|
|
|
|
|
|
In the FIPS provider they are non-approved algorithms and do not have the
|
|
|
|
"fips=yes" property set.
|
2020-05-26 11:53:07 +08:00
|
|
|
No additional parameters can be set during key generation.
|
|
|
|
|
2020-04-15 01:06:12 +08:00
|
|
|
|
|
|
|
=head2 Common X25519, X448, ED25519 and ED448 parameters
|
|
|
|
|
2020-04-20 15:22:41 +08:00
|
|
|
In addition to the common parameters that all keytypes should support (see
|
|
|
|
L<provider-keymgmt(7)/Common parameters>), the implementation of these keytypes
|
|
|
|
support the following.
|
2020-04-15 01:06:12 +08:00
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
|
|
|
=item "pub" (B<OSSL_PKEY_PARAM_PUB_KEY>) <octet string>
|
|
|
|
|
|
|
|
The public key value.
|
|
|
|
|
|
|
|
=item "priv" (B<OSSL_PKEY_PARAM_PRIV_KEY>) <octet string>
|
|
|
|
|
|
|
|
The private key value.
|
|
|
|
|
2020-05-20 23:20:27 +08:00
|
|
|
=item "tls-encoded-pt" (B<OSSL_PKEY_PARAM_TLS_ENCODED_PT>) <octet string>
|
|
|
|
|
|
|
|
Used for getting and setting the encoding of the public key used in a key exchange
|
|
|
|
message for the TLS protocol.
|
|
|
|
|
2020-04-15 01:06:12 +08:00
|
|
|
=back
|
|
|
|
|
2020-04-20 15:29:47 +08:00
|
|
|
=head2 ED25519 and ED448 parameters
|
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
|
|
|
=item "mandatory-digest" (B<OSSL_PKEY_PARAM_MANDATORY_DIGEST>) <utf8 string>
|
|
|
|
|
|
|
|
The empty string, signifying that no digest may be specified.
|
|
|
|
|
|
|
|
=back
|
|
|
|
|
2020-04-15 01:06:12 +08:00
|
|
|
=head1 CONFORMING TO
|
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
|
|
|
=item RFC 8032
|
|
|
|
|
2020-05-26 11:53:07 +08:00
|
|
|
=item RFC 8410
|
|
|
|
|
2020-04-15 01:06:12 +08:00
|
|
|
=back
|
|
|
|
|
|
|
|
=head1 EXAMPLES
|
|
|
|
|
|
|
|
An B<EVP_PKEY> context can be obtained by calling:
|
|
|
|
|
|
|
|
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);
|
|
|
|
|
|
|
|
An B<ED25519> key can be generated like this:
|
|
|
|
|
|
|
|
EVP_PKEY *pkey = NULL;
|
|
|
|
EVP_PKEY_CTX *pctx =
|
|
|
|
EVP_PKEY_CTX_new_from_name(NULL, "ED25519", NULL);
|
|
|
|
|
|
|
|
EVP_PKEY_keygen_init(pctx);
|
|
|
|
EVP_PKEY_gen(pctx, &pkey);
|
|
|
|
EVP_PKEY_CTX_free(pctx);
|
|
|
|
|
|
|
|
An B<X25519> key can be generated in a similar way:
|
|
|
|
|
|
|
|
EVP_PKEY *pkey = NULL;
|
|
|
|
EVP_PKEY_CTX *pctx =
|
|
|
|
EVP_PKEY_CTX_new_from_name(NULL, "X25519", NULL);
|
|
|
|
|
|
|
|
EVP_PKEY_keygen_init(pctx);
|
|
|
|
EVP_PKEY_gen(pctx, &pkey);
|
|
|
|
EVP_PKEY_CTX_free(pctx);
|
|
|
|
|
|
|
|
=head1 SEE ALSO
|
|
|
|
|
|
|
|
L<EVP_KEYMGMT(3)>, L<EVP_PKEY(3)>, L<provider-keymgmt(7)>,
|
|
|
|
L<EVP_KEYEXCH-X25519(7)>, L<EVP_KEYEXCH-X448(7)>,
|
|
|
|
L<EVP_SIGNATURE-ED25519(7)>, L<EVP_SIGNATURE-ED448(7)>
|
|
|
|
|
|
|
|
=head1 COPYRIGHT
|
|
|
|
|
|
|
|
Copyright 2020 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
|
|
|
|
L<https://www.openssl.org/source/license.html>.
|
|
|
|
|
|
|
|
=cut
|