From: Robert Pluim <rpluim@gmail.com>
To: 김민우 <kmwyard@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Getting SSL test A+ grade on elpa.gnu.org
Date: Wed, 25 Nov 2020 18:51:15 +0100 [thread overview]
Message-ID: <87d001wcj0.fsf@gmail.com> (raw)
In-Reply-To: <20201125173812.GD1558@odonien.localdomain> (Vasilij Schneidermann's message of "Wed, 25 Nov 2020 18:38:12 +0100")
Vasilij Schneidermann <mail@vasilij.de> writes:
>> It could have a bad effect on security and privacy for emacs users. Would
>> you apply only TLS 1.3 on elpa.gnu.org?
>
> ITYM TLSv1.2 and upwards. Remember how GNU ELPA merely supporting
> TLSv1.3 required Emacs versions older than 26.3 to apply a workaround to
> successfully establish a connection to GNU ELPA?
Right
> Another thing to watch out for is the cipher suites. To reach a good
> rating several of them need to be disabled and extensive testing is
> required to ensure that we don't exclude users from fetching packages
> for no apparent reason.
The impression I get is that reordering the cipher suite list to put
the weak ones at the end might be enough to improve the score. That
shouldn't create any compatibility issues (and is a good idea
regardless of just 'improving our score').
> Something else I'm curious about, what exactly blocks us from forcing a
> HTTP->HTTPS redirect? Is it waiting for Emacs 26.1 and newer to become a
> widely used Emacs version or are there others?
Are you sure that all the versions of Emacs that connect to
elpa.gnu.org work correctly in the face of such a redirect? What about
versions that donʼt support https?
Robert
next prev parent reply other threads:[~2020-11-25 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 15:11 Getting SSL test A+ grade on elpa.gnu.org 김민우
2020-11-25 17:04 ` Robert Pluim
2020-11-26 6:21 ` 김민우
2020-11-25 17:38 ` Vasilij Schneidermann
2020-11-25 17:51 ` Robert Pluim [this message]
2020-11-25 18:10 ` Vasilij Schneidermann
2020-11-25 18:52 ` Stefan Monnier
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=87d001wcj0.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kmwyard@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).