Hi. On Sat, 15 Apr 2017 15:14:29 +0000 (UTC) david...@freevolt.org wrote:
> On Fri, 14 Apr 2017, Reco wrote: > > > Hi. > > > > On Thu, Apr 13, 2017 at 01:01:24PM -0400, Greg Wooledge wrote: > >> On Thu, Apr 13, 2017 at 11:54:32AM -0500, Martin McCormick wrote: > >>> This started out a year or so ago with the occasional site in > >>> which lynx would report that it was unable to establish a TLS > >>> connection with this or that site. [...] > >> > >> It's not just lynx. It's EVERY single terminal-based browser, and > >> as you noticed, it gets worse every day. > >> > >> Apparently all of the terminal-based browsers in wheezy and jessie are > >> linked with libgnutls instead of libopenssl, and libgnutls (at least as > >> provided by jessie) is completely incapable of forming an SSL connection > >> with half of the Web. > > > > There's one notable exception to this in jessie and it's called w3m. > > > > $ ldd /usr/bin/w3m | grep ssl > > libssl.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 > > In wheezy (at least) I've noticed that curl can also cope, when lynx > (and wget) cannot. AFAIK jessie is the last Debian release that provides curl linked with openssl. Reco