diff options
| author | schwarze <> | 2023-06-06 16:20:13 +0000 |
|---|---|---|
| committer | schwarze <> | 2023-06-06 16:20:13 +0000 |
| commit | e179b69bde328604cd932b1a2e0bf2a4a5e80aba (patch) | |
| tree | ab0ef5aabd72c252da5105c4c32d878302f04f8b /src/regress | |
| parent | 285370c6fda08e1e01791466e6f2562290c804a2 (diff) | |
| download | openbsd-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/regress')
0 files changed, 0 insertions, 0 deletions