guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] doc: cookbook: Update entry about getting substitutes throug


From: Brice Waegeneire
Subject: Re: [PATCH] doc: cookbook: Update entry about getting substitutes through Tor.
Date: Sun, 28 Jun 2020 11:37:32 +0000
User-agent: Roundcube Webmail/1.3.8

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]