Theo Buehler

On Fri, Sep 06, 2024 at 09:30:16AM -0700, orbea wrote: > This patch is enough to build httplib-cpp, but if possible it would be nice to have this working more...

What apart form ccache uses this and needs the OpenSSL support? BoringSSL also doesn't currently have OPENSSL_thread_stop.

ok, thanks for the report and the info. The patch for 0.16.3 looks good. I assume that OpenSSL support is enabled simply because it's the upstream's default.

This diff makes the hanging openssl command work: ```diff --- apps/openssl/req.c.orig Fri Sep 6 13:24:38 2024 +++ apps/openssl/req.c Fri Sep 6 15:42:00 2024 @@ -586,6 +586,9 @@ req_main(int argc, char...

Kind of expected. The argument makes a lot of sense since they added support for BoringSSL which also doesn't support the OpenSSL 3 API.

So I'll see that I can get this req diff into the next release. I don't think the error codes are a particularly interesting thing to look into.

> I'm working on [openTLS](https://github.com/zelang-dev/openTLS) building your `libtls` **only** for the installed **OpenSSL** version, it's being used to develop [c-asio](https://github.com/zelang-dev/c-asio). Many distros already provide libretls: https://git.causal.agency/libretls/about/ > Adding a `atexit()`...

We are open to helping you out in whichever way is acceptable for us, but I'm not sure what we could do in this case other than providing a `tls_cleanup()`...

I am well aware of the atexit handler that OpenSSL installs and also that it has caused numerous issues over the years. I cautioned you against using that approach and...

Thanks for the report. The openssl command line tool is complete garbage and unfit for any purpose. Unfortunately, people keep using it so we must keep it. I envy the...