Re: A potential bug and some questions about TLS

Thomas Dickey <[email protected]> Fri, 4 Jul 2025 15:17:36 -0400
Newsgroups gmane.comp.web.lynx.devel
Message-ID <[email protected]>
On Thu, Jul 03, 2025 at 07:33:54PM -0500, Nate Choe via Lynx-dev wrote:
> Hello everyone!
> 
> I was reading through some of the Lynx source code, and I have some questions
> about how Lynx handles TLS. Specifically, in HTTP.c:734, we see this snippet:
...
> With all of that in mind, I have a few questions:
> 
> 1. Is this intended behavior or just a bug?

It sounds like a bug.

> 2. It seems like Lynx goes out of its way to support legacy versions of OpenSSL.
> Would it be unreasonable to assume that a user has access to the
> SSL_set_max_proto_version, which was added in OpenSSL version 1.1.0?

...only with a suitable configure check.
 
> 3. In a similar vein, would it be unreasonable to drop SSL support entirely?

..probably not.

The real problem is that there's been no stable api, which would allow any
application to just recompile periodically and update painlessly.

We don't have that situation with standardized APIs - SSL/TLS/etc, just seem
to have RFCs which leave too much leeway for implementator of libraries.

(a patch to address the issues you outline would be duly considered - thanks)

-- 
Thomas E. Dickey <[email protected]>
https://invisible-island.net
signature.asc (application/pgp-signature, 659 B)
-----BEGIN PGP SIGNATURE-----

iQGzBAABCgAdFiEEGYgtkt2kxADCLA1WzCr0RyFnvgMFAmhoKNAACgkQzCr0RyFn
vgP0awwA0JU5M3UiC8jlJeO64lh2W+qAv+VPKIY3VqBPjw/+RWw8irTrP9SKuyNw
f2Ni8KOKP8Tf5CnfR7JfUn+vxG0HWG2my10ObK8sOmpIlKgATdg8GuWN517UAjSo
Cb/KAOhmb8/QxcAX4stumGg8CdLDtHTWEHg2/hRDkF9vjyT9M1g3dEcpIePeLv0r
jkA6x2smT/zT8DynTvRPBesnwA1ZkfQ558v2cFwtISpLBR2hYmRbxGpKoPvdDSPy
EO9mX3Kp5M4vMp56GnUgkG6dqG4n+0efb91crCgjtbacMfqqLpj8sDL6xJCFmwXj
Fzrdf7f2+4ah31iPTs4XLIR5sWP2D+p07VBCnCU6Tf9NHUAuYz5eglYeha4m0evp
4T2DYhaFK4owD2BaL+kTlJNSDva3+MS1lRM6Gwiklhvwcmy/ltFKwt9N/WFzqlYy
I4IvHRyBkC4ZaEjGwLx6XdZTIBYbO1vua5y8/LBH/cGHq15NN+9euIXmCi6Zs7wa
hp7LCx6u
=okMv
-----END PGP SIGNATURE-----