summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/X509_STORE_CTX_get_error.3
diff options
context:
space:
mode:
authorschwarze <>2023-06-06 16:20:13 +0000
committerschwarze <>2023-06-06 16:20:13 +0000
commite179b69bde328604cd932b1a2e0bf2a4a5e80aba (patch)
treeab0ef5aabd72c252da5105c4c32d878302f04f8b /src/lib/libcrypto/man/X509_STORE_CTX_get_error.3
parent285370c6fda08e1e01791466e6f2562290c804a2 (diff)
downloadopenbsd-e179b69bde328604cd932b1a2e0bf2a4a5e80aba.tar.gz
openbsd-e179b69bde328604cd932b1a2e0bf2a4a5e80aba.tar.bz2
openbsd-e179b69bde328604cd932b1a2e0bf2a4a5e80aba.zip
In 1995, Eric A. Young chose a confusing name for the "lastUpdate" field
of the X509_CRL_INFO object. It should have been called "thisUpdate" like in RFC 5280 section 5.1 (and in its precursor RFC 2459). Then again, RFC 2459 was only published in 1999, so maybe the terminology wasn't firmly established yet when Young wrote his code several years earlier - just guessing, neither we nor the OpenSSL folks appear to know the real reasons... Anyway, we have been stuck with the "lastUpdate" names in the API for more than two decades now, so clarify in the documentation what they refer to and what they really mean. Requested by and OK tb@.
Diffstat (limited to 'src/lib/libcrypto/man/X509_STORE_CTX_get_error.3')
-rw-r--r--src/lib/libcrypto/man/X509_STORE_CTX_get_error.38
1 files changed, 5 insertions, 3 deletions
diff --git a/src/lib/libcrypto/man/X509_STORE_CTX_get_error.3 b/src/lib/libcrypto/man/X509_STORE_CTX_get_error.3
index b3d0ee3069..1f221563cb 100644
--- a/src/lib/libcrypto/man/X509_STORE_CTX_get_error.3
+++ b/src/lib/libcrypto/man/X509_STORE_CTX_get_error.3
@@ -1,4 +1,4 @@
1.\" $OpenBSD: X509_STORE_CTX_get_error.3,v 1.27 2023/04/30 14:49:47 tb Exp $ 1.\" $OpenBSD: X509_STORE_CTX_get_error.3,v 1.28 2023/06/06 16:20:13 schwarze Exp $
2.\" full merge up to: 2.\" full merge up to:
3.\" OpenSSL man3/X509_STORE_CTX_get_error 24a535ea Sep 22 13:14:20 2020 +0100 3.\" OpenSSL man3/X509_STORE_CTX_get_error 24a535ea Sep 22 13:14:20 2020 +0100
4.\" OpenSSL man3/X509_STORE_CTX_new 24a535ea Sep 22 13:14:20 2020 +0100 4.\" OpenSSL man3/X509_STORE_CTX_new 24a535ea Sep 22 13:14:20 2020 +0100
@@ -68,7 +68,7 @@
68.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED 68.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
69.\" OF THE POSSIBILITY OF SUCH DAMAGE. 69.\" OF THE POSSIBILITY OF SUCH DAMAGE.
70.\" 70.\"
71.Dd $Mdocdate: April 30 2023 $ 71.Dd $Mdocdate: June 6 2023 $
72.Dt X509_STORE_CTX_GET_ERROR 3 72.Dt X509_STORE_CTX_GET_ERROR 3
73.Os 73.Os
74.Sh NAME 74.Sh NAME
@@ -386,7 +386,9 @@ The certificate notBefore field contains an invalid time.
386The certificate notAfter field contains an invalid time. 386The certificate notAfter field contains an invalid time.
387.It Dv X509_V_ERR_ERROR_IN_CRL_LAST_UPDATE_FIELD : \ 387.It Dv X509_V_ERR_ERROR_IN_CRL_LAST_UPDATE_FIELD : \
388 No format error in CRL's lastUpdate field 388 No format error in CRL's lastUpdate field
389The CRL lastUpdate field contains an invalid time. 389The CRL thisUpdate field (sic!) contains an invalid time.
390Both the name of the error constant and the text of the error message
391give a wrong name for the field that contains the problem.
390.It Dv X509_V_ERR_ERROR_IN_CRL_NEXT_UPDATE_FIELD : \ 392.It Dv X509_V_ERR_ERROR_IN_CRL_NEXT_UPDATE_FIELD : \
391 No format error in CRL's nextUpdate field 393 No format error in CRL's nextUpdate field
392The CRL nextUpdate field contains an invalid time. 394The CRL nextUpdate field contains an invalid time.