openbsd/src/lib/libcrypto/stack/safestack.h, branch OPENBSD_7_9_BASEA mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE2024-03-02T11:22:48+00:00Remove a few no longer used sk_FOO_* stanzas2024-03-02T11:22:48+00:00tb2024-03-02T11:22:48+00:00urn:sha1:5be6fed8afd6b03e5a92d68881bc11c7ae195c16
ok jsing
Remove sk_find_ex()2024-03-02T11:20:36+00:00tb2024-03-02T11:20:36+00:00urn:sha1:b56b72805aa516348080e8769435cb6cae2c3c5d
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
Make LHASH_OF() and STACK_OF() use opaque structs2024-03-02T11:11:11+00:00tb2024-03-02T11:11:11+00:00urn:sha1:26367add3db68a3e89bda58a3c85174507f8e71a
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
Remove lh stats2024-03-02T11:04:52+00:00tb2024-03-02T11:04:52+00:00urn:sha1:792421b3f220abcbd1405485edc9bf6b39485769
This could have been removed in an earlier bump. Now it's time for it to
say goodbye.
ok jsing
Remove unused sk/lh macros2023-08-03T16:32:15+00:00tb2023-08-03T16:32:15+00:00urn:sha1:989b85313f728b0b870dc707bb338a96ca53eee3
ok jsing miod
Remove sk_nid_triple_*()2023-07-28T10:26:33+00:00tb2023-07-28T10:26:33+00:00urn:sha1:2bca7fcf4242f1f10d0b696c606387ec84d6ccd0
The nid_triple stack is no more. Its type never was part of the public API.
Why its stack macros were will remain a mystery.
ok jsing
Make ex_data implementations internal2023-07-28T10:19:20+00:00tb2023-07-28T10:19:20+00:00urn:sha1:df077cec5ce229b03845385f6f75dbe7cd5f7080
To state the obvious: library suffers from way too much extensibility. In
theory, applications can implement their own ex_data implementation. In
practice, none did. A glance at ex_data.c might give an idea as to why.
Make this internal so this particular turd can be replaced with something
slightly saner.
Also sync up the CRYPTO_EX_INDEX_* defines with OpenSSL - at least
the parts we support.
ok jsing
Move the policy STACK_OF stuff to pcy_int.h as well2023-04-25T18:53:42+00:00tb2023-04-25T18:53:42+00:00urn:sha1:10ed2aa863bdac9785b93749bd4840b1ed959c38Remove SXNET2023-04-25T18:48:32+00:00tb2023-04-25T18:48:32+00:00urn:sha1:fbf2ba949e9a8593bfac40125b23645ec041759f
Unused and no authorative information was found online in 2016
Future users of libcrypto will also have to do without strong extranet2023-04-24T22:30:17+00:00tb2023-04-24T22:30:17+00:00urn:sha1:bcc671564aeeb25bdf7d30755b4057e14494f592
support.
discussed with beck and jsing