unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Nala Ginrut <mulei@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Support rsync to help Chinese users to setup mirrors
Date: Fri, 09 Aug 2019 10:52:02 +0200	[thread overview]
Message-ID: <87ef1uwwjx.fsf@elephly.net> (raw)
In-Reply-To: <87ef1usx58.fsf@debian>


Nala Ginrut <mulei@gnu.org> writes:

>> Would rsync over SSH be sufficient or does it have to be rsyncd on the
>> default rsync port?  (SSH will be easier for me because then I don’t
>> need to apply for another port to be opened at the institute firewall.)
>
> I think SSH will be interfered frequently by the firewall, because many
> people use SSH for anti-circumvention. It's better to use rsyncd.
> Considering there's verification, so the encryption is unnecessary.

Oh pity.  Back then I did in fact use SSH tunnels to get around the
great firewall; VPNs were the primary target back then.

rsyncd is going to take longer as I need to make an application to the
campus IT to let them open the port.  I’ll let you know when it’s ready,
but it can take a little while.

--
Ricardo

  reply	other threads:[~2019-08-09  8:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 10:56 Support rsync to help Chinese users to setup mirrors Nala Ginrut
2019-08-01 14:22 ` Ricardo Wurmus
2019-08-02  7:35   ` Nala Ginrut
2019-08-07  6:31     ` Nala Ginrut
2019-08-07  7:44       ` Ricardo Wurmus
2019-08-08  9:35         ` Nala Ginrut
2019-08-08 11:39           ` Ricardo Wurmus
2019-08-08 18:56             ` Nala Ginrut
2019-08-08 21:35               ` Ricardo Wurmus
2019-08-09  5:52                 ` Nala Ginrut
2019-08-09  8:52                   ` Ricardo Wurmus [this message]
2019-08-10  8:18                     ` Nala Ginrut

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=87ef1uwwjx.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=mulei@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).