<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libcrypto/x509, branch OPENBSD_7_5</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=OPENBSD_7_5</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=OPENBSD_7_5'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2024-03-02T11:20:36+00:00</updated>
<entry>
<title>Remove sk_find_ex()</title>
<updated>2024-03-02T11:20:36+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T11:20:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=b56b72805aa516348080e8769435cb6cae2c3c5d'/>
<id>urn:sha1:b56b72805aa516348080e8769435cb6cae2c3c5d</id>
<content type='text'>
This API intends to find the closest match to the needle. M2Crypto
exposes it because it can. This will be fixed by patching the port.

ok jsing
</content>
</entry>
<entry>
<title>Make LHASH_OF() and STACK_OF() use opaque structs</title>
<updated>2024-03-02T11:11:11+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T11:11:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=26367add3db68a3e89bda58a3c85174507f8e71a'/>
<id>urn:sha1:26367add3db68a3e89bda58a3c85174507f8e71a</id>
<content type='text'>
This removes internals of these two special snowflakes and will allow
further simplifications. Unfortunately, there are some pieces of
software that actually use LHASH_OF() (looking at you, pound, Ruby, and
openssl(1)), so we get to keep exposing this garbage, at least for now.

Expose lh_error() as a symbol to replace a macro reaching into _LHASH.
lh_down_load() is no longer available. _LHASH and _STACK are now opaque,
LHASH_NODE becomes internal-only.

from jsing
</content>
</entry>
<entry>
<title>Remove X509_CRL_METHOD API</title>
<updated>2024-03-02T10:59:41+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T10:59:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=af88f8de5f2275485734ca59b90ee42b81b76688'/>
<id>urn:sha1:af88f8de5f2275485734ca59b90ee42b81b76688</id>
<content type='text'>
I would keep repeating myself... In the bit bucket you go.

ok jsing
</content>
</entry>
<entry>
<title>Garbage collect most of the public LOOKUP API</title>
<updated>2024-03-02T10:57:03+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T10:57:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=71f803228f85a85e040f88d8df2af4393f0d64c6'/>
<id>urn:sha1:71f803228f85a85e040f88d8df2af4393f0d64c6</id>
<content type='text'>
Yet another bit of extensibility that no one ever really used.
X509_LOOKUP_free() needs to stay because of ... rust-openssl
(and kdelibs4support).

ok jsing
</content>
</entry>
<entry>
<title>Expose X509_STORE_get1_objects()</title>
<updated>2024-03-02T10:54:39+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T10:54:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=674fe4ef9bc076029351013b920100f4c1cbfb40'/>
<id>urn:sha1:674fe4ef9bc076029351013b920100f4c1cbfb40</id>
<content type='text'>
Safer replacement API for the unsafe X509_STORE_get0_objects().

ok jsing
</content>
</entry>
<entry>
<title>Make X509_CERT_AUX internal</title>
<updated>2024-03-02T10:52:24+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T10:52:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=e6bd45a92fad0a48bfefcef615d89af3225724c4'/>
<id>urn:sha1:e6bd45a92fad0a48bfefcef615d89af3225724c4</id>
<content type='text'>
Another struct/API that should never have leaked out of the library.

ok jsing
</content>
</entry>
<entry>
<title>Remove X509_TRUST from the public API</title>
<updated>2024-03-02T10:50:26+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T10:50:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=a13c3d8a59554d7330ef94cc9d8a5049fb8602fe'/>
<id>urn:sha1:a13c3d8a59554d7330ef94cc9d8a5049fb8602fe</id>
<content type='text'>
With API and other users internal, this struct can now go.

ok jsing
</content>
</entry>
<entry>
<title>Remove DECLARE_STACK_OF(X509_TRUST)</title>
<updated>2024-03-02T10:49:03+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T10:49:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=2870b50968a01fdfa5f8d86f84057dad1464712d'/>
<id>urn:sha1:2870b50968a01fdfa5f8d86f84057dad1464712d</id>
<content type='text'>
Unused since the extensibility was neutered.

ok jsing
</content>
</entry>
<entry>
<title>Remove unused public X509_TRUST API</title>
<updated>2024-03-02T10:48:17+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T10:48:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=bd61e1e1013cfd2b6462e4fbf774072eb184c44c'/>
<id>urn:sha1:bd61e1e1013cfd2b6462e4fbf774072eb184c44c</id>
<content type='text'>
Another thing that should never have leaked out of the library. It
will become internal entirely, where the code can be simplified greatly.

ok jsing
</content>
</entry>
<entry>
<title>const correct X509_PURPOSE_get0{,_{,s}name}()</title>
<updated>2024-03-02T10:43:52+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T10:43:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=83f478fb201e647181d2250ce31e9359bdca5065'/>
<id>urn:sha1:83f478fb201e647181d2250ce31e9359bdca5065</id>
<content type='text'>
Unfortunately, PHP and rust-openssl still need this API. At least we
can make the table read-only now since we disabled its extensibility.

ok jsing
</content>
</entry>
</feed>
