summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/EVP_VerifyInit.3
diff options
context:
space:
mode:
authorschwarze <>2024-11-08 22:23:35 +0000
committerschwarze <>2024-11-08 22:23:35 +0000
commitc3ee0949bc29213b45f00440a3e7849bf65608c1 (patch)
tree0d3c20fc4d228dfe84edecb7cdbbb3accc5b85f5 /src/lib/libcrypto/man/EVP_VerifyInit.3
parentaef80d57f4c4c17e8936fb0426aca8800f62d831 (diff)
downloadopenbsd-c3ee0949bc29213b45f00440a3e7849bf65608c1.tar.gz
openbsd-c3ee0949bc29213b45f00440a3e7849bf65608c1.tar.bz2
openbsd-c3ee0949bc29213b45f00440a3e7849bf65608c1.zip
Weed out the last remaining refences to the obsolete
function EVP_MD_CTX_init(3) and talk about EVP_MD_CTX_new(3) instead. This is similar in spirit to OpenSSL commit 25191fff (Dec 1, 2015), but i'm also mentioning EVP_MD_CTX_reset(3), slightly reordering some sentences in a more systematic way, and improving some related wordings to be more precise and read better.
Diffstat (limited to 'src/lib/libcrypto/man/EVP_VerifyInit.3')
-rw-r--r--src/lib/libcrypto/man/EVP_VerifyInit.324
1 files changed, 13 insertions, 11 deletions
diff --git a/src/lib/libcrypto/man/EVP_VerifyInit.3 b/src/lib/libcrypto/man/EVP_VerifyInit.3
index dfebe8f2bf..0baadfb9fb 100644
--- a/src/lib/libcrypto/man/EVP_VerifyInit.3
+++ b/src/lib/libcrypto/man/EVP_VerifyInit.3
@@ -1,6 +1,5 @@
1.\" $OpenBSD: EVP_VerifyInit.3,v 1.12 2024/07/21 08:36:43 tb Exp $ 1.\" $OpenBSD: EVP_VerifyInit.3,v 1.13 2024/11/08 22:23:35 schwarze Exp $
2.\" full merge up to: OpenSSL b97fdb57 Nov 11 09:33:09 2016 +0100 2.\" full merge up to: OpenSSL 24a535ea Sep 22 13:14:20 2020 +0100
3.\" selective merge up to: OpenSSL 79b49fb0 Mar 20 10:03:10 2018 +1000
4.\" 3.\"
5.\" This file was written by Dr. Stephen Henson <steve@openssl.org>. 4.\" This file was written by Dr. Stephen Henson <steve@openssl.org>.
6.\" Copyright (c) 2000, 2001, 2006, 2016 The OpenSSL Project. 5.\" Copyright (c) 2000, 2001, 2006, 2016 The OpenSSL Project.
@@ -50,7 +49,7 @@
50.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED 49.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
51.\" OF THE POSSIBILITY OF SUCH DAMAGE. 50.\" OF THE POSSIBILITY OF SUCH DAMAGE.
52.\" 51.\"
53.Dd $Mdocdate: July 21 2024 $ 52.Dd $Mdocdate: November 8 2024 $
54.Dt EVP_VERIFYINIT 3 53.Dt EVP_VERIFYINIT 3
55.Os 54.Os
56.Sh NAME 55.Sh NAME
@@ -86,20 +85,23 @@
86.Fa "const EVP_MD *type" 85.Fa "const EVP_MD *type"
87.Fc 86.Fc
88.Sh DESCRIPTION 87.Sh DESCRIPTION
89The EVP signature verification routines are a high level interface to 88The EVP signature verification routines are a high-level interface to
90digital signatures. 89digital signatures.
91.Pp 90.Pp
92.Fn EVP_VerifyInit_ex 91.Fn EVP_VerifyInit_ex
93sets up a verification context 92sets up the verification context
94.Fa ctx 93.Fa ctx
95to use the digest 94to use the digest
96.Fa type . 95.Fa type .
96Before calling this function, obtain
97.Fa ctx 97.Fa ctx
98must be initialized by calling 98from
99.Xr EVP_MD_CTX_init 3 99.Xr EVP_MD_CTX_new 3
100before calling this function. 100or call
101.Xr EVP_MD_CTX_reset 3
102on it.
101The 103The
102.Fa ENGINE *engine 104.Fa engine
103argument is always ignored and passing 105argument is always ignored and passing
104.Dv NULL 106.Dv NULL
105is recommended. 107is recommended.
@@ -132,7 +134,7 @@ to use the default implementation of digest
132.Fa type . 134.Fa type .
133.Pp 135.Pp
134The EVP interface to digital signatures should almost always be 136The EVP interface to digital signatures should almost always be
135used in preference to the low level interfaces. 137used in preference to the low-level interfaces.
136This is because the code then becomes transparent to the algorithm used 138This is because the code then becomes transparent to the algorithm used
137and much more flexible. 139and much more flexible.
138.Pp 140.Pp