From: Jason Vas Dias <jason.vas.dias@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: eww + w3m / GnuTLS TLSv1 support ?
Date: Tue, 15 Feb 2022 12:52:43 +0000 [thread overview]
Message-ID: <CALyZvKwqSXkbiUFiwwMPKfMZY0m7yDWFhd-OeY9hhVYp=c6-eQ@mail.gmail.com> (raw)
In-Reply-To: <CAO2hHWb07GBKUUStTQOeYgy4w3mpsO3D5RiLw0c5ZdGbQ2aJdQ@mail.gmail.com>
OK, I finally fixed it for firefox & whole OpenSSL or GnuTLS
using stack on Fedora 34+ : as root:
# update-crypto-policies --set DEFAULT:DEFAULT
but that on its own did not work without making the
changes to /usr/share/crypto-policies/policies/DEFAULT.pol
in the attached patch file, then restarting firefox with
the about:config options:
security.tls.version.enable-deprecated true
security.tls.version.min 1
Now I can access TLSv1 websites, and my modem,
with firefox - and also with GnuTLS / Emacs - wahoo!
The best website to test this with is :
https://tls-v1-0.badssl.com:1010/
Thanks to all who responded !
On 14/02/2022, chad <yandros@gmail.com> wrote:
> On Sun, Feb 13, 2022 at 9:58 AM Jason Vas Dias <jason.vas.dias@gmail.com>
> wrote:
>
>> I need to access the website of a modem which ONLY supports
>> TLS Version 1.0 [...] https://192.168.1.1 [...]
>>
>
> Orthogonal to eww/gnutls support: in your position, I would (curse a bit
> and) look into a local https proxy, starting with mitmproxy or tinyproxy.
> I've been able to use solutions like this in the past, but that past is now
> distant, and I don't know what's current. I see downstream you ask about
> some nodeJS options; there's probably a relevant node project that you
> could set up inside your local network.
>
> Hope that helps,
> ~Chad
>
next prev parent reply other threads:[~2022-02-15 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 14:58 eww + w3m / GnuTLS TLSv1 support ? Jason Vas Dias
2022-02-13 15:44 ` Herbert J. Skuhra
2022-02-13 16:48 ` Jason Vas Dias
2022-02-13 17:07 ` Eli Zaretskii
2022-02-14 12:34 ` Jason Vas Dias
2022-02-14 13:25 ` Herbert J. Skuhra
2022-02-14 13:36 ` Jason Vas Dias
2022-02-14 18:51 ` chad
2022-02-15 12:52 ` Jason Vas Dias [this message]
2022-02-15 12:55 ` Jason Vas Dias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALyZvKwqSXkbiUFiwwMPKfMZY0m7yDWFhd-OeY9hhVYp=c6-eQ@mail.gmail.com' \
--to=jason.vas.dias@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).