openbsd/src/lib/libcrypto/opensslfeatures.h, branch OPENBSD_7_9A mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_7_92024-08-31T10:38:49+00:00Nuke the whrlpool (named after the galaxy) from orbit2024-08-31T10:38:49+00:00tb2024-08-31T10:38:49+00:00urn:sha1:74a335fca70cbc1c69a8939c41ad12d0a6414a99
It's just gross. Only used by a popular disk encryption utility on an
all-too-popular OS one or two decades back.
ok beck jsing
Update list of OPENSSL_NO_*2024-03-02T11:25:46+00:00tb2024-03-02T11:25:46+00:00urn:sha1:65016a97383151d0c0d604f03bf28b322382ab40
This syncs the list with some version of upstream and exposes a few
OPENSSL_NO_* that may now be relevant.
from jsing (a long time ago)
Unhook and remove GOST and STREEBOG2024-03-02T11:17:27+00:00tb2024-03-02T11:17:27+00:00urn:sha1:8ea5a70cb7cc8a88e0f55a52b08b9bf917e9ab4d
This stops compiling the GOST source. The current implementation is low
quality and got in the way, especially in libssl. While we would be open
for GOST support, it needs to be significantly better than what we have
had and it also needs a maintainer.
Add OPENSSL_NO_GOST to opensslfeatures and stop installing gost.h.
Some code wrapped in #ifndef OPENSSL_NO_GOST will be removed later.
ok jsing
Set OPENSSL_NO_ENGINE, remove engine code2023-07-28T09:53:55+00:00tb2023-07-28T09:53:55+00:00urn:sha1:b5382a6334a2ec0fe73ab6c49ebefb47af93329c
ENGINE was special. It's horrible code even by the low standards of this
library. Some ports may now try to use the stubs which will fail, but
the fallout from this should be minimal. Of course there are various
language bindings that expose the ENGINE API. OpenSSL 3 disabling ENGINE
by default will likely help fixing this at some point.
ok jsing
Drop DSO and define OPENSSL_NO_DSO2023-07-28T09:46:36+00:00tb2023-07-28T09:46:36+00:00urn:sha1:f94d1800c2bcef623d825d9ec18437897e187e0e
DSO and in particular dlopen() was used for dynamic engines, which we
removed a long time ago and for dynamic conf modules, which we removed
only very recently. Now remove this dangerous interface.
ok jsing
define OPENSSL_NO_DTLS1_1 since we no longer have that either.2023-07-06T06:38:01+00:00beck2023-07-06T06:38:01+00:00urn:sha1:86e9fdb1f24e39ab0ee179d5efcd68a28ed9c2af
ok tb@
Define the 'standard' OPENSSL_NO_BLAHBLAH's for no tls 1.0 or 1.12023-07-06T06:15:36+00:00beck2023-07-06T06:15:36+00:00urn:sha1:9cbf6fca419db1aac8facd72f628352a2bdc6e8c
We have no tls 1.0 or 1.1 or methods for them.
These "in theory" will make things that check the openssl #ifdef
soup for all the floating eyeballs make the correct decisions, or
if they do not they at least can not blame us.
ok tb@
Remove commented version of OPENSSL_NO_EC2M2023-04-25T19:34:06+00:00tb2023-04-25T19:34:06+00:00urn:sha1:9f55dbfa70be8c40062f910dc88aea15e06244afLIBRESSL_NEXT_API is no longer needed2023-04-25T19:29:36+00:00tb2023-04-25T19:29:36+00:00urn:sha1:b79c6954d86ef0c9b626d3104645a9ac27d93072Temporarily define LIBRESSL_NEXT_API in opensslfeatures.h2023-04-25T15:50:09+00:00tb2023-04-25T15:50:09+00:00urn:sha1:d56aae88fbe08aeee80528571c4bdc6a91727db9