unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vasilij Schneidermann <mail@vasilij.de>
To: emacs-devel@gnu.org
Subject: Enforcing TLS for GNU ELPA
Date: Tue, 20 Oct 2020 00:10:20 +0200	[thread overview]
Message-ID: <20201019221020.GD1842@odonien.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

Some time ago I've contributed a change to a certain package
repository's webserver setup that responds to http:// requests with a
301 redirect to the https:// version.  Should the same be done for GNU
ELPA?  Why/why not?

Some data points for the "why not" faction I've discovered after that
change:

- There's still Windows users who do not have an installation with the
  gnutls libraries, despite the strong suggestion to download it for the
  full experience.
- Emacs versions below 26.1 are affected by a HTTPS proxy bug [1] that
  makes life in corporate environments hard.
- The initializer of `package-archives` already generates the
  appropriate URL, so this will affect people who have redefined that
  variable and break their setup for no reason.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-10-19 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 22:10 Vasilij Schneidermann [this message]
2020-10-19 22:20 ` Enforcing TLS for GNU ELPA Vasilij Schneidermann
2020-10-19 22:30 ` Stefan Monnier
2020-10-20  7:50   ` tomas
2020-10-20  9:05 ` Jean Louis
2020-10-20 10:07   ` Vasilij Schneidermann
2020-10-20 11:38     ` Jean Louis

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=20201019221020.GD1842@odonien.localdomain \
    --to=mail@vasilij.de \
    --cc=emacs-devel@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 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).