From: Brice Waegeneire <brice@waegenei.re>
To: "André Batista" <nandre@riseup.net>
Cc: guix-devel@gnu.org,
Guix-devel <guix-devel-bounces+brice+lists=waegenei.re@gnu.org>
Subject: Re: [PATCH] doc: cookbook: Update entry about getting substitutes through Tor.
Date: Sun, 28 Jun 2020 11:37:32 +0000 [thread overview]
Message-ID: <62389fabcbf7f40b03cca0d85446a704@waegenei.re> (raw)
In-Reply-To: <20200618140611.GA2613@andel>
Hello André,
On 2020-06-18 14:06, André Batista wrote:
[...]
> qua 17 jun 2020 às 08:37:59 (1592393879), brice@waegenei.re enviou:
>> I would like to keep the warnings at the beginning of the section
>> to be sure that readers don't miss it when skimming trough it.
>> Any rewording of that part to make the scope of the section or
>> the warnings more clear is welcome.
>
> It follows attached a new version of the previous patch which
> changes the comment to the warning quote. I had previously thought
> that it would be worse to inflate the warning with this comment even
> more so as the section's title already mentions it's related to
> substitutes.
I tought I already had applied your patch, but I forgot to do it.
It's now applied as f8945734a5abff69644284231cc47fb67456657b, sorry
for the delay.
[...]
>> On a wider front I would prefer to have a foolproof configuration
>> that route *all* guix related traffic through Tor, instead of that
>> half-way setup. Providing a way to 'torify' any service with
>> something like 'make-forkexec-constructor/trosocks', as
>> 'make-forkexec-constructor/container' does for containerizing a
>> service, would be great[0]. A less engaged option would be to
>> make 'guix-daemon' compatible with 'torsocks' since doing it so
>> makes guix unusable[1].
>
> I too would prefer it, but a half-way setup is what we have for now.
> So a three-quarters-way would be an improvement though not the fix
> we're in need. I'll dig deeper and will come back to you if I make
> any progress.
I would love to know when you manage to advance on that front.
Have a good day,
- Brice
next prev parent reply other threads:[~2020-06-28 11:37 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
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 [this message]
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=62389fabcbf7f40b03cca0d85446a704@waegenei.re \
--to=brice@waegenei.re \
--cc=guix-devel-bounces+brice+lists=waegenei.re@gnu.org \
--cc=guix-devel@gnu.org \
--cc=nandre@riseup.net \
/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).