| EVP_PKEY_new.pod (1.1.1.5) | EVP_PKEY_new.pod (1.1.1.6) |
|---|---|
| 1=pod 2 3=head1 NAME 4 5EVP_PKEY, 6EVP_PKEY_new, 7EVP_PKEY_up_ref, 8EVP_PKEY_dup, --- 48 unchanged lines hidden (view full) --- 57 EVP_PKEY *EVP_PKEY_new_CMAC_key(ENGINE *e, const unsigned char *priv, 58 size_t len, const EVP_CIPHER *cipher); 59 60=head1 DESCRIPTION 61 62B<EVP_PKEY> is a generic structure to hold diverse types of asymmetric keys 63(also known as "key pairs"), and can be used for diverse operations, like 64signing, verifying signatures, key derivation, etc. The asymmetric keys | 1=pod 2 3=head1 NAME 4 5EVP_PKEY, 6EVP_PKEY_new, 7EVP_PKEY_up_ref, 8EVP_PKEY_dup, --- 48 unchanged lines hidden (view full) --- 57 EVP_PKEY *EVP_PKEY_new_CMAC_key(ENGINE *e, const unsigned char *priv, 58 size_t len, const EVP_CIPHER *cipher); 59 60=head1 DESCRIPTION 61 62B<EVP_PKEY> is a generic structure to hold diverse types of asymmetric keys 63(also known as "key pairs"), and can be used for diverse operations, like 64signing, verifying signatures, key derivation, etc. The asymmetric keys |
| 65themselves are often refered to as the "internal key", and are handled by | 65themselves are often referred to as the "internal key", and are handled by |
| 66backends, such as providers (through L<EVP_KEYMGMT(3)>) or B<ENGINE>s. 67 68Conceptually, an B<EVP_PKEY> internal key may hold a private key, a public 69key, or both (a keypair), and along with those, key parameters if the key type 70requires them. The presence of these components determine what operations can 71be made; for example, signing normally requires the presence of a private key, 72and verifying normally requires the presence of a public key. 73 --- 131 unchanged lines hidden (view full) --- 205The EVP_PKEY_new_CMAC_key() was deprecated in OpenSSL 3.0. 206 207The documentation of B<EVP_PKEY> was amended in OpenSSL 3.0 to allow there to 208be the private part of the keypair without the public part, where this was 209previously implied to be disallowed. 210 211=head1 COPYRIGHT 212 | 66backends, such as providers (through L<EVP_KEYMGMT(3)>) or B<ENGINE>s. 67 68Conceptually, an B<EVP_PKEY> internal key may hold a private key, a public 69key, or both (a keypair), and along with those, key parameters if the key type 70requires them. The presence of these components determine what operations can 71be made; for example, signing normally requires the presence of a private key, 72and verifying normally requires the presence of a public key. 73 --- 131 unchanged lines hidden (view full) --- 205The EVP_PKEY_new_CMAC_key() was deprecated in OpenSSL 3.0. 206 207The documentation of B<EVP_PKEY> was amended in OpenSSL 3.0 to allow there to 208be the private part of the keypair without the public part, where this was 209previously implied to be disallowed. 210 211=head1 COPYRIGHT 212 |
| 213Copyright 2002-2021 The OpenSSL Project Authors. All Rights Reserved. | 213Copyright 2002-2023 The OpenSSL Project Authors. All Rights Reserved. |
| 214 215Licensed under the Apache License 2.0 (the "License"). You may not use 216this file except in compliance with the License. You can obtain a copy 217in the file LICENSE in the source distribution or at 218L<https://www.openssl.org/source/license.html>. 219 220=cut | 214 215Licensed under the Apache License 2.0 (the "License"). You may not use 216this file except in compliance with the License. You can obtain a copy 217in the file LICENSE in the source distribution or at 218L<https://www.openssl.org/source/license.html>. 219 220=cut |