From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: The SHA1 sunset
Date: Mon, 04 Jan 2016 23:15:56 +0100 [thread overview]
Message-ID: <m3twmtvvmr.fsf@gnus.org> (raw)
In-Reply-To: <m2oad2888i.fsf@newartisans.com> (John Wiegley's message of "Sun, 03 Jan 2016 17:05:17 -0800")
John Wiegley <jwiegley@gmail.com> writes:
>>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> On the fourth hand, we release Emacs so seldomly that we have to plan for
>> the future, so perhaps it should be in "medium" anyway.
>
> Yeah, that was my thinking.
Mm. I wonder what the percentage of TLS certificates are SHA-1 these
days... anybody have statistics?
A user just discovered that the (self-signed) certificate on
news.gmane.org is SHA-1, for instance. :-)
>> It would have been nice if Emacs had a way to retroactively change these
>> things. I mean, "push" very, very selective security-related updates on
>> users... Hm... could we imagine using the package system for doing security
>> updates? It would mean that Emacs would "call home" once in a while...
>
> Or associate your warnings with times, and after a certain date being
> proclaiming that doom is likely upon them.
:-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-01-04 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 9:55 The SHA1 sunset Lars Magne Ingebrigtsen
2016-01-03 15:37 ` Eli Zaretskii
2016-01-03 19:58 ` John Wiegley
2016-01-04 0:53 ` Lars Magne Ingebrigtsen
2016-01-04 1:05 ` John Wiegley
2016-01-04 22:15 ` Lars Magne Ingebrigtsen [this message]
2016-01-04 2:10 ` Mike Gerwitz
2016-01-04 22:14 ` Lars Magne Ingebrigtsen
2016-01-05 6:38 ` Mike Gerwitz
2016-01-05 7:07 ` Lars Magne Ingebrigtsen
2016-01-04 15:42 ` Eli Zaretskii
2016-01-04 23:04 ` James Cloos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3twmtvvmr.fsf@gnus.org \
--to=larsi@gnus.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.