[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: eww + w3m / GnuTLS TLSv1 support ?
From: |
Herbert J. Skuhra |
Subject: |
Re: eww + w3m / GnuTLS TLSv1 support ? |
Date: |
Sun, 13 Feb 2022 16:44:07 +0100 |
On Sun, Feb 13, 2022 at 02:58:15PM +0000, Jason Vas Dias wrote:
> Good day -
>
> I need to access the website of a modem which ONLY supports
> TLS Version 1.0 - the only CURL options that work for it
> are :
> $ curl -ik --tlsv1.0 --basic -u$USER':'$PASS 'https://192.168.1.1'
> ( options '--tlsv1.'{1,2,3} NO NOT WORK AT ALL ! )
> OpenSSL s_client also works with ONLY the '-tls1' option
> (but does not do the HTTP Basic Auth as curl does).
>
> I only have access to my up-to-date Fedora 34 Linux x86_64 host,
> or my Android Phone on the WiFi network it serves with hostapd.
>
> It has been the case for a while that Firefox / Chrome for Linux
> do not permit me to use TLS-v1 - only Windows 10's Internet Explorer
> used to work, when run from a Qemu/KVM Windows VM under Linux - but now,
> with latest Windows 10 update, even this support has been removed.
>
> So my only home internet connection router's operations / management
> web-page is now completely inaccessable to me from any of 6 modern browsers
> I have installed on Linux or Windows :
> ( latest Firefox, latest Chrome, w3m , eww, lynx, MS-Edge, MS-IE ) -
> none of them support TLSv1.0 .
Have you tried to set
security.tls.version.enable-deprecated to true
in Firefox (about:config)?
This still works with Firefox 97.0 and an old(er) SNOM 300 SIP phone.
I have created a separate Firefox profile for this use case.
Maybe other solutions like stunnel, etc. might work too.
--
Herbert
Re: eww + w3m / GnuTLS TLSv1 support ?, chad, 2022/02/14