all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: bo0od <bo0od@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 47647@debbugs.gnu.org
Subject: bug#47647: Feature request: Make guix communicate over Hidden Services
Date: Tue, 20 Apr 2021 18:20:09 +0000	[thread overview]
Message-ID: <b1fda2f9-8489-563c-b8f9-97a5231012c7@riseup.net> (raw)
In-Reply-To: <87fszkc3r8.fsf@gnu.org>

Yeah but how can someone create Tor mirror to guix upstream/main 
repository if its not done by the upstream themselves?

Unless user make his own server and get all guix packages there in order 
for him to have Tor-Tor connection from his own server/repository which 
is crazy amount of effort compared to just mounting the upstream main 
server (same server not different one) to Tor.

Having clearnet and Tor entries for same server way much easier to 
create new server just for Tor.

Ludovic Courtès:
> Hi,
> 
> bo0od <bo0od@riseup.net> skribis:
> 
>> Yeah not clean connection, What i meant by this feature sorry i didnt
>> say it clearer at the the first text which is Guix main repository
>> guix-git must be mirrored over tor hidden services then when using
>> guix install or guix pull or ...etc is going to be all over Tor (no
>> TLS used).
> 
> OK, this is what the cookbook entry proposes, right?
> 
> The missing bit is accessing the Git repo of the ‘guix’ channel via an
> Onion service (for ‘guix pull’), though one can easily create such a
> mirror.
> 
> HTH,
> Ludo’.
> 




      reply	other threads:[~2021-04-20 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 23:30 bug#47647: Feature request: Make guix communicate over Hidden Services bo0od
2021-04-19 16:39 ` Ludovic Courtès
2021-04-19 18:13   ` bo0od
2021-04-20 16:36     ` Ludovic Courtès
2021-04-20 18:20       ` bo0od [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b1fda2f9-8489-563c-b8f9-97a5231012c7@riseup.net \
    --to=bo0od@riseup.net \
    --cc=47647@debbugs.gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.