GNU bug report logs - #53941
27.2; socks + tor dont work with https

Previous Next

Full log

View this message in rfc822 format

From: "J.P." <jp <at> neverwas.me>
To: 53941 <at> debbugs.gnu.org
Cc: larsi <at> gnus.org, gnuhacker <at> member.fsf.org, Eli Zaretskii <eliz <at> gnu.org>, Stefan Kangas <stefankangas <at> gmail.com>
Subject: bug#53941: 27.2; socks + tor dont work with https
Date: Sat, 09 Sep 2023 07:05:12 -0700

[Message part 1 (text/plain, inline)]

I seem to have missed the fact that `url-methods' populates the option
`url-proxy-services' from environment variables when initializing
`url-scheme-registry'. As explained in the docs, it actually accepts
full URLs instead of just host:port pairs. I take this to mean it's
probably less disruptive than initially thought to extend this liberty
to `url-proxy-services' itself. I've updated the POC patches to reflect
this, so it should now be possible to do:

    (setenv "HTTPS_PROXY" "socks5h://localhost:9050")
    (eww "https://check.torproject.org/")

Of course, this shouldn't interfere with traditional http proxies, such
as those that provide CONNECT tunneling:

    $ ncat -l --proxy-type http localhost 8888
    (setenv "HTTPS_PROXY" "localhost:8888")
    (eww "https://www.example.com/")

[0000-v4-v5.diff (text/x-patch, attachment)]

[0001-Don-t-hard-code-server-ports-in-SOCKS-tests.patch (text/x-patch, attachment)]

[0002-Improve-SOCKS-error-handling-and-add-support-for-4a.patch (text/x-patch, attachment)]

[0003-POC-Simplify-network-stream-openers-in-socks.el.patch (text/x-patch, attachment)]

[0004-POC-Integrate-the-socks-and-url-libraries.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.