summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/EVP_PKEY_CTX_ctrl.3
diff options
context:
space:
mode:
Diffstat (limited to 'src/lib/libcrypto/man/EVP_PKEY_CTX_ctrl.3')
-rw-r--r--src/lib/libcrypto/man/EVP_PKEY_CTX_ctrl.311
1 files changed, 6 insertions, 5 deletions
diff --git a/src/lib/libcrypto/man/EVP_PKEY_CTX_ctrl.3 b/src/lib/libcrypto/man/EVP_PKEY_CTX_ctrl.3
index 0ed3678a99..0c30fcb5ef 100644
--- a/src/lib/libcrypto/man/EVP_PKEY_CTX_ctrl.3
+++ b/src/lib/libcrypto/man/EVP_PKEY_CTX_ctrl.3
@@ -1,4 +1,4 @@
1.\" $OpenBSD: EVP_PKEY_CTX_ctrl.3,v 1.5 2016/11/27 15:27:19 schwarze Exp $ 1.\" $OpenBSD: EVP_PKEY_CTX_ctrl.3,v 1.6 2016/12/25 22:15:10 schwarze Exp $
2.\" OpenSSL e03af178 Dec 11 17:05:57 2014 -0500 2.\" OpenSSL e03af178 Dec 11 17:05:57 2014 -0500
3.\" 3.\"
4.\" This file was written by Dr. Stephen Henson <steve@openssl.org>. 4.\" This file was written by Dr. Stephen Henson <steve@openssl.org>.
@@ -49,7 +49,7 @@
49.\" 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
50.\" OF THE POSSIBILITY OF SUCH DAMAGE. 50.\" OF THE POSSIBILITY OF SUCH DAMAGE.
51.\" 51.\"
52.Dd $Mdocdate: November 27 2016 $ 52.Dd $Mdocdate: December 25 2016 $
53.Dt EVP_PKEY_CTX_CTRL 3 53.Dt EVP_PKEY_CTX_CTRL 3
54.Os 54.Os
55.Sh NAME 55.Sh NAME
@@ -205,9 +205,10 @@ Two RSA padding modes behave differently if
205.Fn EVP_PKEY_CTX_set_signature_md 205.Fn EVP_PKEY_CTX_set_signature_md
206is used. 206is used.
207If this macro is called for PKCS#1 padding, the plaintext buffer is an 207If this macro is called for PKCS#1 padding, the plaintext buffer is an
208actual digest value and is encapsulated in a DigestInfo structure 208actual digest value and is encapsulated in a
209according to PKCS#1 when signing and this structure is expected (and 209.Vt DigestInfo
210stripped off) when verifying. 210structure according to PKCS#1 when signing and this structure is
211expected (and stripped off) when verifying.
211If this control is not used with RSA and PKCS#1 padding then the 212If this control is not used with RSA and PKCS#1 padding then the
212supplied data is used directly and not encapsulated. 213supplied data is used directly and not encapsulated.
213In the case of X9.31 padding for RSA the algorithm identifier byte is 214In the case of X9.31 padding for RSA the algorithm identifier byte is