From: Robert Pluim <rpluim@gmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
Emacs developers <Emacs-devel@gnu.org>
Subject: Re: preferring https: to http: in commit messages for gnu.org
Date: Mon, 16 Oct 2017 18:20:13 +0200 [thread overview]
Message-ID: <874lqzrrnm.fsf@gmail.com> (raw)
In-Reply-To: <CAP_d_8UbqfSq3JeU-2NjCZivYmAAvs8Cs4KCunbNiPVTia7_ZA@mail.gmail.com> (Yuri Khan's message of "Mon, 16 Oct 2017 22:19:03 +0700")
Yuri Khan <yuri.v.khan@gmail.com> writes:
> On Mon, Oct 16, 2017 at 10:09 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> That includes URLs such as
>>
>> http://lists.gnu.org/archive/html/emacs-devel/2017-10/msg00592.html
>>
>>> The goal is for developers to have reliable communications
>>> from the GNU project itself, even if other sources are less reliable.
>
> A good first step towards that goal is to configure the server at
> http://lists.gnu.org/* to serve a permanent redirect to
> https://lists.gnu.org/*.
No, a good first step is to upgrade https://lists.gnu.org to use TLS
1.2 instead of 1.0, then we can start thinking about redirects and/or
enforcing https spelling in commits. eg Mozilla in paranoid mode will
refuse to connect to TLS 1.0 sites, with no override available
Robert
next prev parent reply other threads:[~2017-10-16 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 7:14 preferring https: to http: in commit messages for gnu.org Paul Eggert
2017-10-15 14:25 ` Eli Zaretskii
2017-10-16 7:07 ` Paul Eggert
2017-10-16 15:09 ` Eli Zaretskii
2017-10-16 15:19 ` Yuri Khan
2017-10-16 16:20 ` Robert Pluim [this message]
2017-10-16 18:47 ` Paul Eggert
2017-10-16 18:54 ` Eli Zaretskii
2017-10-16 23:15 ` Paul Eggert
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lqzrrnm.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=Emacs-devel@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=yuri.v.khan@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).