From: Simo Sorce <simo@redhat.com>
Date: Tue, 15 Apr 2025 19:21:19 +0000 (-0400)
Subject: Fix EVP_PKEY_verify man page
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=58dfbe34e1b43233bf37f1c2a47622c46532cedd;p=thirdparty%2Fopenssl.git

Fix EVP_PKEY_verify man page

Various functions were misnamed in the descriptions.

Signed-off-by: Simo Sorce <simo@redhat.com>

Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/27342)
---

diff --git a/doc/man3/EVP_PKEY_verify.pod b/doc/man3/EVP_PKEY_verify.pod
index e5bd70a90d2..94d15a332a7 100644
--- a/doc/man3/EVP_PKEY_verify.pod
+++ b/doc/man3/EVP_PKEY_verify.pod
@@ -50,31 +50,31 @@ I<ctx> for verifying an unlimited size message using the algorithm given by
 I<algo> and the key given through L<EVP_PKEY_CTX_new(3)> or
 L<EVP_PKEY_CTX_new_from_pkey(3)>.
 Passing the message is supported both in a one-shot fashion using
-EVP_PKEY_verify(), and through the combination of EVP_PKEY_verify_update() and
-EVP_PKEY_verify_final().
+EVP_PKEY_verify(), and through the combination of
+EVP_PKEY_verify_message_update() and EVP_PKEY_verify_message_final().
 This function enables using algorithms that can process input of arbitrary
 length, such as ED25519, RSA-SHA256 and similar.
 
 EVP_PKEY_CTX_set_signature() specifies the I<siglen> bytes long signature
-I<sig> to be verified against by EVP_PKEY_verify_final().
-It I<must> be used together with EVP_PKEY_verify_update() and
-EVP_PKEY_verify_final().
+I<sig> to be verified against by EVP_PKEY_verify_message_final().
+It I<must> be used together with EVP_PKEY_verify_message_update() and
+EVP_PKEY_verify_message_final().
 See L</NOTES> below for a deeper explanation.
 
-EVP_PKEY_verify_update() adds I<inlen> bytes from I<in> to the data to be
-processed for verification.  The signature algorithm specification and
+EVP_PKEY_verify_message_update() adds I<inlen> bytes from I<in> to the data
+to be processed for verification.  The signature algorithm specification and
 implementation determine how the input bytes are processed and if there's a
 limit on the total size of the input.  See L</NOTES> below for a deeper
 explanation.
 
-EVP_PKEY_verify_final() verifies the processed data, given only I<ctx>.
+EVP_PKEY_verify_message_final() verifies the processed data, given only I<ctx>.
 The signature to verify against must have been given with
 EVP_PKEY_CTX_set_signature().
 
 EVP_PKEY_verify() is a one-shot function that performs the same thing as
 EVP_PKEY_CTX_set_signature() call with I<sig> and I<siglen> as parameters,
-followed by a single EVP_PKEY_verify_update() call with I<tbs> and I<tbslen>,
-followed by EVP_PKEY_verify_final() call.
+followed by a single EVP_PKEY_verify_message_update() call with I<tbs> and
+I<tbslen>, followed by EVP_PKEY_verify_message_final() call.
 
 =head1 NOTES