unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Prefer https: for GNU and FSF URLs
Date: Fri, 29 Sep 2017 16:37:05 +0100	[thread overview]
Message-ID: <alpine.DEB.2.00.1709291634040.12020@tp.orcam.me.uk> (raw)
In-Reply-To: <18cce39e-4a5a-27d8-a1ca-5ec45973088e@cs.ucla.edu>

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?

  Maciej


  parent reply	other threads:[~2017-09-29 15:37 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 [this message]
2017-09-29 16:59   ` Jonathan Nieder
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=alpine.DEB.2.00.1709291634040.12020@tp.orcam.me.uk \
    --to=macro@imgtec.com \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-alpha@sourceware.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.
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).