From: "Ludovic Courtès" <ludo@gnu.org>
To: Brice Waegeneire <brice@waegenei.re>
Cc: guix-devel@gnu.org
Subject: Re: Routing Guix services traffic trough Tor
Date: Mon, 18 May 2020 00:33:44 +0200 [thread overview]
Message-ID: <87blmmkx87.fsf@gnu.org> (raw)
In-Reply-To: <887f7538354a77d0df85cb3f458ffac4@waegenei.re> (Brice Waegeneire's message of "Tue, 12 May 2020 17:22:54 +0000")
Hi Brice,
Brice Waegeneire <brice@waegenei.re> skribis:
> Today I played a bit with Tor and Guix, trying to fetch substitutes
> trough
> the Tor network as blaze_cornbread asked on IRC[0] how to do this. I
> managed to get it working but in the end I don't think we should
> encourage
> people doing it this way, that's why I haven't submitted a patch to the
> cookbook for it. Currently the only supported way to proxy traffic for
> 'guix-daemon' is by setting a HTTP proxy[1] the drawback is that DNS
> query
> will still be in clear and wont go trough the proxy in contrast to a
> SOCKS5
> proxy where the query will happen on the other side of the proxy.
I don’t think that’s the case: when an HTTP proxy is in use, clients
make a CONNECT or GET HTTP request to the proxy, which resolves the host
name on their behalf. That’s why you can pass
‘--substitute-urls=http://bp7o7ckwlewr4slm.onion’ and it Just Works.
So I think you message could make a great section in the cookbook. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-05-17 22:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 17:22 Routing Guix services traffic trough Tor Brice Waegeneire
2020-05-17 22:33 ` Ludovic Courtès [this message]
2020-05-18 20:32 ` Brice Waegeneire
2020-05-24 21:04 ` Ludovic Courtès
2020-06-03 19:12 ` [PATCH] doc: cookbook: Add entry about getting substitutes through Tor Brice Waegeneire
2020-06-04 12:29 ` [bug#41694] " Ludovic Courtès
2020-06-04 12:54 ` Brice Waegeneire
2020-06-17 2:19 ` André Batista
2020-06-17 8:37 ` Brice Waegeneire
2020-06-18 14:06 ` [PATCH] doc: cookbook: Update " André Batista
2020-06-28 11:37 ` Brice Waegeneire
2020-07-03 20:30 ` André Batista
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blmmkx87.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=brice@waegenei.re \
--cc=guix-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/guix.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).