From c1e350577fe14e3e124cc258f742cb77a14b6ce8 Mon Sep 17 00:00:00 2001 From: Richard Levitte Date: Sat, 19 Mar 2016 11:39:47 +0100 Subject: [PATCH] Correct faulty L<> links in .pods Closes RT#4450 Reviewed-by: Rich Salz --- doc/crypto/EVP_EncryptInit.pod | 6 +++--- doc/crypto/X509_LOOKUP_hash_dir.pod | 2 +- doc/ssl/SSL_CTX_set_read_ahead.pod | 2 +- doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod | 9 +++++---- 4 files changed, 10 insertions(+), 9 deletions(-) diff --git a/doc/crypto/EVP_EncryptInit.pod b/doc/crypto/EVP_EncryptInit.pod index 1b39e83961..b42b64c178 100644 --- a/doc/crypto/EVP_EncryptInit.pod +++ b/doc/crypto/EVP_EncryptInit.pod @@ -384,13 +384,13 @@ bits and 12 rounds. AES Galois Counter Mode (GCM) for 128, 192 and 256 bit keys respectively. These ciphers require additional control operations to function correctly: see -the L section below for details. +the L section below for details. =item EVP_aes_128_ocb(void), EVP_aes_192_ocb(void), EVP_aes_256_ocb(void) Offest Codebook Mode (OCB) for 128, 192 and 256 bit keys respectively. These ciphers require additional control operations to function correctly: see -the L section below for details. +the L section below for details. =item EVP_aes_128_ccm(), EVP_aes_192_ccm(), EVP_aes_256_ccm() @@ -441,7 +441,7 @@ length can only be set before specifying an IV. If not called a default tag length is used. For OCB AES the default is 16 (i.e. 128 bits). This is also the maximum tag length for OCB. -See L below for an example of the use of GCM mode. +See L below for an example of the use of GCM mode. =head1 CCM Mode diff --git a/doc/crypto/X509_LOOKUP_hash_dir.pod b/doc/crypto/X509_LOOKUP_hash_dir.pod index e863ab5a87..dfb9e214e4 100644 --- a/doc/crypto/X509_LOOKUP_hash_dir.pod +++ b/doc/crypto/X509_LOOKUP_hash_dir.pod @@ -47,7 +47,7 @@ B. Constant B with NULL filename causes these functions to load default certificate store file (see -L. +L. Functions return number of objects loaded from file or 0 in case of diff --git a/doc/ssl/SSL_CTX_set_read_ahead.pod b/doc/ssl/SSL_CTX_set_read_ahead.pod index f7d8c43357..771d59d604 100644 --- a/doc/ssl/SSL_CTX_set_read_ahead.pod +++ b/doc/ssl/SSL_CTX_set_read_ahead.pod @@ -39,7 +39,7 @@ ahead has been set or not. These functions have no impact when used with DTLS. The return values for SSL_CTX_get_read_head() and SSL_get_read_ahead() are undefined for DTLS. Setting B can impact the behaviour of the SSL_pending() function -(see L). +(see L). =head1 RETURN VALUES diff --git a/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod b/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod index e8b973f238..b660b21a9a 100644 --- a/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod +++ b/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod @@ -49,11 +49,12 @@ I, and set the cipher context I and the hash context I. The I is 16 characters long and is used as a key identifier. The I length is the length of the IV of the corresponding cipher. The -maximum IV length is L bytes defined in B. +maximum IV length is B bytes defined in B. The initialization vector I should be a random value. The cipher context I should use the initialisation vector I. The cipher context can be -set using L. The hmac context can be set using L. +set using L. The hmac context can be set using +L. When the client presents a session ticket, the callback function with be called with I set to 0 indicating that the I function should retrieve a set @@ -61,8 +62,8 @@ of parameters. In this case I and I have already been parsed out of the session ticket. The OpenSSL library expects that the I will be used to retrieve a cryptographic parameters and that the cryptographic context I will be set with the retrieved parameters and the initialization vector -I. using a function like L. The I needs to be set -using L. +I. using a function like L. The I needs to be +set using L. If the I is still valid but a renewal of the ticket is required the callback function should return 2. The library will call the callback again -- 2.25.1