> On Dec 8, 2021, at 22:42, Craig A. Berry <craig.a.berry@gmail.com> wrote: > > But > is there any reason other than it's hard work that Perl shouldn't > include Net::SSLeay, IO::Socket::SSL, and Mozilla::CA in the core and > build them whenever the underlying support is available? It occurs to me (as I’ve been learning mbedTLS) is that IO::Socket::SSL explicitly wraps Net::SSLeay/OpenSSL/LibreSSL. ISTM a more ideal pattern would be some library-agnostic mechanism that doesn’t privilege one TLS library over another. Curl, for example, can use OpenSSL, GnuTLS, wolfSSL, NSS, mbedTLS, Secure Transport, or any of several others. I know of no such abstraction on CPAN now, in December 2021, but I thought it still worth mentioning. -FGThread Previous | Thread Next