<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libcrypto/hidden, branch libressl-v3.9.1</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=libressl-v3.9.1</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=libressl-v3.9.1'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2024-03-02T13:39:28+00:00</updated>
<entry>
<title>Remove some GOST relics</title>
<updated>2024-03-02T13:39:28+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T13:39:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=b67dd091b5f82f671c4de5665606d30a7de36db5'/>
<id>urn:sha1:b67dd091b5f82f671c4de5665606d30a7de36db5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Make CRYPTO_THREADID opaque</title>
<updated>2024-03-02T11:37:13+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T11:37:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=17579c0eb7910d89f824a0cb4f9967d3af8a04ac'/>
<id>urn:sha1:17579c0eb7910d89f824a0cb4f9967d3af8a04ac</id>
<content type='text'>
With ERR_STATE out of the way, we can make CRYPTO_THREADID opaque.
The type is still accessed by used public API, but some of the public
API can also go away.

ok jsing
</content>
</entry>
<entry>
<title>Remove CRYPTO_*info</title>
<updated>2024-03-02T11:32:31+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T11:32:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=442f5bad00cacf2ea72b97c3bdfe8b35b23ada3c'/>
<id>urn:sha1:442f5bad00cacf2ea72b97c3bdfe8b35b23ada3c</id>
<content type='text'>
Long time neutered, only used (pointlessly without error checking) in the
error code until very recently.

ok jsing
</content>
</entry>
<entry>
<title>Remove a bunch of CRYPTO memory API</title>
<updated>2024-03-02T11:28:46+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T11:28:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=0b6deb78b28f14c6fe58749806ff4e6774c9cbe9'/>
<id>urn:sha1:0b6deb78b28f14c6fe58749806ff4e6774c9cbe9</id>
<content type='text'>
This was neutered early on in the fork and has been rotting ever since.
Some parts of the API are still used, but it's easier to clean up when
most of the mess is gone.

ok jsing
</content>
</entry>
<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 lh stats</title>
<updated>2024-03-02T11:04:52+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T11:04:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=792421b3f220abcbd1405485edc9bf6b39485769'/>
<id>urn:sha1:792421b3f220abcbd1405485edc9bf6b39485769</id>
<content type='text'>
This could have been removed in an earlier bump. Now it's time for it to
say goodbye.

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>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>Remove unused parts of the purpose API</title>
<updated>2024-03-02T10:40:05+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-03-02T10:40:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7b018fc829c78dbce4b7cd8a28aa798b3e03d6a4'/>
<id>urn:sha1:7b018fc829c78dbce4b7cd8a28aa798b3e03d6a4</id>
<content type='text'>
Most of this is the ability to add custom purposes. Also the astounding
X509_STORE_CTX_purpose_inherit(). The names are used by PHP, and M2Crypto
exposes X509_check_purpose(), so these remain public. Some weird, most
likely invalid, uses also remain in rust-openssl.

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