NAME<\/a> evp \u2212 high\u2212level cryptographic functions<\/p>\n #include The EVP<\/small> library provides a high-level interface to cryptographic functions.<\/p>\n The EVP_Seal<\/b> XXX<\/small><\/i> and EVP_Open<\/b> XXX<\/small><\/i> functions provide public key encryption and decryption to implement digital “envelopes”.<\/p>\n The EVP_DigestSign<\/b> XXX<\/small><\/i> and EVP_DigestVerify<\/b> XXX<\/small><\/i> functions implement digital signatures and Message Authentication Codes (MACs). Also see the older EVP_Sign<\/b> XXX<\/small><\/i> and EVP_Verify<\/b> XXX<\/small><\/i> functions.<\/p>\n Symmetric encryption is available with the EVP_Encrypt<\/b> XXX<\/small><\/i> functions. The EVP_Digest<\/b> XXX<\/small><\/i> functions provide message digests.<\/p>\n The EVP_PKEY<\/small><\/b>XXX<\/i><\/small> functions provide a high-level interface to asymmetric algorithms. To create a new EVP_PKEY<\/small> see EVP_PKEY_new<\/b>(3). EVP_PKEYs can be associated with a private key of a particular algorithm by using the functions described on the EVP_PKEY_set1_RSA<\/b>(3) page, or new keys can be generated using EVP_PKEY_keygen<\/b>(3). EVP_PKEYs can be compared using EVP_PKEY_cmp<\/b>(3), or printed using EVP_PKEY_print_private<\/b>(3).<\/p>\n The EVP_PKEY<\/small> functions support the full range of asymmetric algorithm operations: The EVP_BytesToKey<\/b>(3) function provides some limited support for password based encryption. Careful selection of the parameters will provide a PKCS#5 PBKDF1<\/small> compatible implementation. However, new applications should not typically use this (preferring, for example, PBKDF2<\/small> from PCKS#5).<\/p>\n The EVP_Encode<\/b> XXX<\/small><\/i> and EVP_Decode<\/b> XXX<\/small><\/i> functions implement base 64 encoding and decoding.<\/p>\n All the symmetric algorithms (ciphers), digests and asymmetric algorithms (public key algorithms) can be replaced by ENGINE<\/small> modules providing alternative implementations. If ENGINE<\/small> implementations of ciphers or digests are registered as defaults, then the various EVP<\/small> functions will automatically use those implementations automatically in preference to built in software implementations. For more information, consult the engine<\/b>(3) man page.<\/p>\n Although low-level algorithm specific functions exist for many algorithms their use is discouraged. They cannot be used with an ENGINE<\/small> and ENGINE<\/small> versions of new algorithms cannot be accessed using the low-level functions. Also makes code harder to adapt to new algorithms and some options are not cleanly supported at the low-level and some operations are more efficient using the high-level interface.<\/p>\n EVP_DigestInit<\/b>(3), EVP_EncryptInit<\/b>(3), EVP_OpenInit<\/b>(3), EVP_SealInit<\/b>(3), EVP_DigestSignInit<\/b>(3), EVP_SignInit<\/b>(3), EVP_VerifyInit<\/b>(3), EVP_EncodeInit<\/b>(3), EVP_PKEY_new<\/b>(3), EVP_PKEY_set1_RSA<\/b>(3), EVP_PKEY_keygen<\/b>(3), EVP_PKEY_print_private<\/b>(3), EVP_PKEY_decrypt<\/b>(3), EVP_PKEY_encrypt<\/b>(3), EVP_PKEY_sign<\/b>(3), EVP_PKEY_verify<\/b>(3), EVP_PKEY_verify_recover<\/b>(3), EVP_PKEY_derive<\/b>(3), EVP_BytesToKey<\/b>(3), ENGINE_by_id<\/b>(3)<\/p>\n Copyright 2000\u22122020 The OpenSSL Project Authors. All Rights Reserved.<\/p>\n Licensed under the OpenSSL license (the “License”). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE<\/small> in the source distribution or at evp \u2212 high\u2212level cryptographic functions <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[971],"tags":[973,1002,972],"class_list":["post-3908","post","type-post","status-publish","format-standard","hentry","category-7-miscelanea","tag-973","tag-evp","tag-man7"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3908","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3908"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3908\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3908"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3908"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3908"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
SYNOPSIS<\/a>
DESCRIPTION<\/a>
SEE ALSO<\/a>
COPYRIGHT<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
For key agreement see EVP_PKEY_derive<\/b>(3)
For signing and verifying see EVP_PKEY_sign<\/b>(3), EVP_PKEY_verify<\/b>(3) and
EVP_PKEY_verify_recover<\/b>(3). However, note that these functions do not
perform a digest of the data to be signed. Therefore, normally you
would use the EVP_DigestSignInit<\/b>(3) functions for this purpose.
For encryption and decryption see EVP_PKEY_encrypt<\/b>(3) and
EVP_PKEY_decrypt<\/b>(3) respectively. However, note that these functions
perform encryption and decryption only. As public key encryption is an
expensive operation, normally you would wrap an encrypted message in a
“digital envelope” using the EVP_SealInit<\/b>(3) and EVP_OpenInit<\/b>(3)
functions.<\/p>\nSEE ALSO <\/a> <\/h2>\n
COPYRIGHT <\/a> <\/h2>\n
\n","protected":false},"excerpt":{"rendered":"