openbsd/src/lib/libcrypto/man, branch masterA mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=master2026-03-10T05:50:11+00:00Fix BIO_get_mem_data(3) return value documentation2026-03-10T05:50:11+00:00tb2026-03-10T05:50:11+00:00urn:sha1:bacb84818745f09c40699821c03ba8a247b2bbac
pointed out by/ok dlg
EVP_SealInit.3: fix RETURN VALUES section2026-01-30T14:33:33+00:00tb2026-01-30T14:33:33+00:00urn:sha1:638e4f9b1442547b8847e1f03dd2903f1eedb08b
While normal calls return 0 for error and npubk for success, there is a
case where it returns the usual 1/0 thing. Make that explicit.
Prompted by a report by Niels Dossche
ok jsing kenjiro
EVP_OpenInit.3: fix RETURN VALUES section2026-01-30T14:26:04+00:00tb2026-01-30T14:26:04+00:00urn:sha1:37888d726bf851fed1c3db8d08652e1dafb02feb
This has been incorrectly documented since forever. The function only ever
returned 0/1.
ok jsing kenjiro
Remove STABLE_FLAGS_MALLOC2025-12-31T13:48:01+00:00tb2025-12-31T13:48:01+00:00urn:sha1:6f2ee5a9a79b7b50dcd481715ff4209cfb40223c
Formerly used by ASN1_STRING_TABLE_{add,cleanup}() which were removed two
years ago. Annotate why STABLE_NO_MASK stays: as usual, security/xca ends
up being the sole consumer of some nonsense. Apparently it needs its own
reimplementation of ASN1_STRING_set_by_NID(), another removable public API
that should never have been exposed.
ok kenjiro
Stop documenting V_ASN1_APP_CHOOSE quirk2025-12-21T09:36:35+00:00tb2025-12-21T09:36:35+00:00urn:sha1:aeda0452754dd4d98535834e7eee39f43767058a
ok kenjiro
This function have -> This function has2025-12-20T11:51:28+00:00tb2025-12-20T11:51:28+00:00urn:sha1:da73d37897fbff0da9bb07f593a26b12ab9fdae1These function -> These functions2025-12-20T08:51:56+00:00tb2025-12-20T08:51:56+00:00urn:sha1:7c469809b7d6b2ba84cd1c79621eccf137404085This functions -> This function2025-12-20T08:40:47+00:00tb2025-12-20T08:40:47+00:00urn:sha1:6c4ae1b16cce99200bfa5d25d54de647709afe21pkcs7: add PKCS7_NO_DUAL_CONTENT flag/behavior2025-12-20T07:22:43+00:00tb2025-12-20T07:22:43+00:00urn:sha1:4e99a5c0b6fa18eb76160d4cb726840aacb45404
What Netscape fucked up just had to be embraced by secure boot and
other nonsense. First OpenSSL wanted to be strict (which we inherited)
then Rich Salz Postel-ized this and made OpenSSL bypass this check by
default and added a flag to be strict 10 years ago.
Now sthen found that PHP 8.5 uses/exposes this flag.
Follows OpenSSL 6b2ebe43 (2016)
ok kenjiro
BN_get_word(): return (BN_ULONG)-1 on error rather than BN_MASK22025-12-15T12:09:46+00:00tb2025-12-15T12:09:46+00:00urn:sha1:341829195e0c845cf26339768f275f021b69fedc
While the latter is more general in that it also works on 1-complement
achitectures, we don't care about that. Adjust documentation and the
only error check for it in libcrypto.
ok deraadt