A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE 2025-04-25T20:04:09+00:00 2025-04-25T20:04:09+00:00 tb 2025-04-25T20:04:09+00:00 urn:sha1:d8e9bf5a12a3b9b7adfb018a7bde8747af650526 2024-12-07T19:22:15+00:00 schwarze 2024-12-07T19:22:15+00:00 urn:sha1:3a3c37739b37d7bbcd87bc316e5af3e47d169240 Not that this would be particularly important, but i had to look at the code anyway while completing the EVP documentation. 2023-05-01T07:37:45+00:00 tb 2023-05-01T07:37:45+00:00 urn:sha1:bd5e4e7792ecd625a77bb630b235191d9dca510f This was the last public API explicitly named ndef/NDEF for indefinite length encoding, so remove that explanation as well. 2022-02-04T00:55:52+00:00 tb 2022-02-04T00:55:52+00:00 urn:sha1:095291972dd2ee176e32630c3077548c07396d57 2021-12-31T22:40:40+00:00 jsg 2021-12-31T22:40:40+00:00 urn:sha1:aee0263de189ae8799986671a950eacc7976d4fe 2021-12-09T15:11:48+00:00 schwarze 2021-12-09T15:11:48+00:00 urn:sha1:53a86468b4d3ddf4f914daab98cd34efef50fb6d There is no need to explain well-known acronyms that are widely used outside OpenSSL, too (like AES, ASN.1, CMS, ECDSA, PKCS...), but OpenSSL uses plenty of idiosyncratic naming elements that deserve to be explained (like d2i, ex, get0, ndef, sk, ...). Requested by jsing@; feedback and OK tb@. 2020-06-24T17:00:38+00:00 schwarze 2020-06-24T17:00:38+00:00 urn:sha1:3567e55107118142b02eb08a87a1298951877be3 OK tb@ 2020-06-24T16:06:27+00:00 schwarze 2020-06-24T16:06:27+00:00 urn:sha1:3ecaa6869c66e0625873e061793893fe06d63dc7 OK tb@ 2019-11-02T15:28:04+00:00 schwarze 2019-11-02T15:28:04+00:00 urn:sha1:8ce3d0166753049e6d22a4aa255ecddf542ccdc8 2019-08-28T10:37:42+00:00 schwarze 2019-08-28T10:37:42+00:00 urn:sha1:162bae9b2695b73db0a85e0625e3bfecfa4c1eab