all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Mike Gerwitz <mtg@gnu.org>, Alex Vong <alexvong1995@gmail.com>,
	guix-devel@gnu.org
Subject: Re: Changing guix download page from using HTTP to HTTPS
Date: Sun, 5 Mar 2017 19:47:53 +0000	[thread overview]
Message-ID: <20170305194753.li4reyojfihesmd2@abyayala> (raw)
In-Reply-To: <20170305194507.dmnt5t4uirjpdoj5@abyayala>

On 17-03-05 19:45:07, ng0 wrote:
> On 17-03-05 13:25:47, Mike Gerwitz wrote:
> > On Sun, Mar 05, 2017 at 16:32:16 +0000, ng0 wrote:
> > > As it is, it is inaccessible for tor users. This would fix it.
> > 
> > The FTP server you mean?  rms has asked the FSF sysadmins to fix this as
> > of a day or two ago, so hopefully that'll work soon.
> > 
> > -- 
> > Mike Gerwitz
> > Free Software Hacker+Activist | GNU Maintainer & Volunteer
> > GPG: D6E9 B930 028A 6C38 F43B  2388 FEF6 3574 5E6F 6D05
> > Old: 2217 5B02 E626 BC98 D7C0  C2E5 F22B B815 8EE3 0EAB
> > https://mikegerwitz.com
> 
> 
> No, this won't fix the fact that port 21+20, the ones commonly used for
> ftp, are commonly blocked by most relays. Switching to http OR https and
> not making ftp the legacy protocol of choice will help here.
> Unless rms went by my recommendation to offer onion services, but all I
> know is that they are talking at the moment.
> 

Sorry, I thought this was a very selective reply to the patch for the
website I've sent today. But my reply still stands.

  reply	other threads:[~2017-03-05 18:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05 15:15 Changing guix download page from using HTTP to HTTPS Alex Vong
2017-03-05 16:32 ` ng0
2017-03-05 18:25   ` Mike Gerwitz
2017-03-05 19:45     ` ng0
2017-03-05 19:47       ` ng0 [this message]
2017-03-06  4:26   ` Alex Vong
2017-03-06  9:07     ` ng0
2017-03-05 18:36 ` Leo Famulari
2017-03-05 18:38 ` Leo Famulari
2017-03-06 10:20   ` Ludovic Courtès

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=20170305194753.li4reyojfihesmd2@abyayala \
    --to=contact.ng0@cryptolab.net \
    --cc=alexvong1995@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mtg@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.