Hi, The AmigaOS 3 build uses AmiSSL (OpenSSL doesn't connect to any sites for some years on that platform for some reason). As long as it is building against AmiSSL 5.x it will be using the OpenSSL 3 API. I did update the SDK to v5 but I think it needs somebody to forcibly rebuild it.
Chris 8 Feb 2024 20:48:24 John-Mark Bell <j...@netsurf-browser.org>: > On 08/02/2024 20:32, NetSurf Browser Project (Commit Mailer) wrote: >> Gitweb links: >> ...log >> http://git.netsurf-browser.org/netsurf.git/shortlog/6bb70e88108c904d67e9af7c8e5b273f6cd6854f >> ...commit >> http://git.netsurf-browser.org/netsurf.git/commit/6bb70e88108c904d67e9af7c8e5b273f6cd6854f >> ...tree >> http://git.netsurf-browser.org/netsurf.git/tree/6bb70e88108c904d67e9af7c8e5b273f6cd6854f >> The branch, jmb/ssl-purge has been created >> at 6bb70e88108c904d67e9af7c8e5b273f6cd6854f (commit) >> - Log ----------------------------------------------------------------- >> commitdiff >> http://git.netsurf-browser.org/netsurf.git/commit/?id=6bb70e88108c904d67e9af7c8e5b273f6cd6854f >> commit 6bb70e88108c904d67e9af7c8e5b273f6cd6854f >> Author: John-Mark Bell <j...@netsurf-browser.org> >> Commit: John-Mark Bell <j...@netsurf-browser.org> >> fetchers: drop support for ancient OpenSSL >> We now require 1.1.1 or later (and, preferably, 3.x). >> Also take the opportunity to add support for LibreSSL 3.5.0 or >> later (we still support ancient versions of this because 3.5.0 is >> still relatively modern -- give it a few more years and support >> for old LibreSSL can go, too) > > [...] > > This builds fine for me against both OpenSSL 1.1.1 and 3.x. All our SDKs > contain 3.x so CI builds that use it should also be fine. However, I've not > actually tested LibreSSL and I believe at least one of the Amiga builds uses > AmiSSL. > > Can people who care about these things take a look at this change and ensure > it works for you? > > Ta, > > > John-Mark.
