openbsd, branch libressl-v3.8.1A mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=libressl-v3.8.12023-08-30T10:13:12+00:00Ensure no memory is leaked after passing NULL to ASN1_TIME_normalize()2023-08-30T10:13:12+00:00job2023-08-30T10:13:12+00:00urn:sha1:1b9ecfa7cff0a57d523522d8d77745aaebf3da47
OK tb@
Document EVP_{CIPHER,MD}_do_all{,_sorted}(3)2023-08-30T00:58:57+00:00tb2023-08-30T00:58:57+00:00urn:sha1:4c47d74088a8ab2b15c21d17abfac6e8d60cf2e8
The function prototypes in the SYNOPSIS don't look great, but schwarze
assures me that this is how it is supposed to be. It is rather strange
that OpenSSL chose to sprinkle OPENSSL_init_crypto() calls into these
four functions rather than two inside OBJ_NAME_do_all{,_sorted}(3).
Surely there was a good reason for that.
With input and fixes from schwarze
Fix leaks in copy_issuer()2023-08-30T00:49:32+00:00tb2023-08-30T00:49:32+00:00urn:sha1:a4768fca91b9eaa7e7367f0ccf398b87f09e1fb8
The stack of subject alternative names from the issuer is parsed using
X509V3_EXT_d2i(), so it must be freed with sk_GENERAL_NAME_pop_free().
It's not worth doing complicated ownership handling when the individual
alternative names can be copied with GENERAL_NAME_dup().
Previously, ialt and its remaining members would be leaked when the call
to sk_GENERAL_NAME_push() failed halfway through.
This is only reachable via the issuer:copy x509v3.cnf(5) directive.
ok jsing
Replace last ecdh.h and ecdsa.h occurrences with ec.h2023-08-29T10:07:42+00:00tb2023-08-29T10:07:42+00:00urn:sha1:09dcbefdff671a2602d306db8c2ca196ca43a8d7
Except if backward compatibility with older LibreSSL and OpenSSL versions
is explicitly needed, ecdsa.h and ecdh.h should no longer be used. They
are now trivial wrappers of ec.h.
Move the weak SHA-1 and MD5 hashes out of EVP_DigestInit(3)2023-08-27T15:33:08+00:00schwarze2023-08-27T15:33:08+00:00urn:sha1:44e1ad16951d32b584361dfd5f8ecee255a20c70
into a new EVP_sha1(3) manual page, and also mention EVP_md4(3) there.
Using input from tb@ and jsing@, who like the general direction.
document the return value of EVP_PKEY_asn1_find(3) and2023-08-27T13:23:12+00:00schwarze2023-08-27T13:23:12+00:00urn:sha1:9c05c884a801c11fd0795c5ef24b2c422487860e
the "len" argument and the return value of EVP_PKEY_asn1_find_str(3)
EVP_PKEY_set_type_str(3) is now documented, so switch from .Fn to .Xr2023-08-27T13:15:29+00:00schwarze2023-08-27T13:15:29+00:00urn:sha1:bf89b1a93addfb188bd48351c468a612376a518edocument EVP_PKEY_set_type_str(3)2023-08-27T13:08:15+00:00schwarze2023-08-27T13:08:15+00:00urn:sha1:4b3c9bbd5a61105dfef24d0ec9c54e86037e7869add the missing information that and how flags can be combined,2023-08-26T15:14:28+00:00schwarze2023-08-26T15:14:28+00:00urn:sha1:01e5981e401d9dac8e212b507619f6d469f2310d
and add the missing link to evp(3)
Write documentation for EVP_CIPHER_CTX_buf_noconst(3) from scratch.2023-08-26T15:12:04+00:00schwarze2023-08-26T15:12:04+00:00urn:sha1:693e666182065ae33f7c13986a8fa11deec65891
Put it here rather than into EVP_EncryptInit(3) because similar to
EVP_CIPHER_CTX_get_cipher_data(3), application software should not
use it. These functions will likely not be needed except by people
implementing custom encryption algorithms.