unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Prefer https: for GNU and FSF URLs
Date: Fri, 29 Sep 2017 09:59:05 -0700	[thread overview]
Message-ID: <20170929165905.GH19555@aiede.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1709291634040.12020@tp.orcam.me.uk>

Hi,

Maciej W. Rozycki wrote:
> Hi Paul,

>> The attached patches adjust glibc to prefer https: in URLs for gnu.org and
>> fsf.org. FTP is being decommissioned soon for gnu.org, and although the GNU
>> project files are not secret, plain HTTP is vulnerable to malicious routers
>> that intercept responses from GNU servers, and this sort of thing is all too
>> common when people in some other countries browse US-based websites.
>
> What's wrong with FTP, especially as given what you have stated it seems
> useful for people beyond myself, and not merely (as it is in my case) for
> convenience reasons?

FTP is vulnerable to mitm in the same way as HTTP is.

Thanks and hope that helps,
Jonathan


  reply	other threads:[~2017-09-29 16:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22  4:24 [PATCH] Prefer https: for GNU and FSF URLs Paul Eggert
2017-09-22 11:47 ` Joseph Myers
2019-09-07 10:06   ` Paul Eggert
2019-09-07 10:22     ` Paul Eggert
2019-09-09 16:28       ` Joseph Myers
2019-09-09 17:45         ` Florian Weimer
2019-09-09 16:27     ` Joseph Myers
2019-09-09 21:18       ` Paul Eggert
2017-09-22 12:13 ` Zack Weinberg
2017-09-29 15:37 ` Maciej W. Rozycki
2017-09-29 16:59   ` Jonathan Nieder [this message]
2017-10-04 23:19     ` Maciej W. Rozycki

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://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=20170929165905.GH19555@aiede.mtv.corp.google.com \
    --to=jrnieder@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-alpha@sourceware.org \
    --cc=macro@imgtec.com \
    /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. 
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).