From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Mike Gerwitz <mtg@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The SHA1 sunset
Date: Tue, 05 Jan 2016 08:07:39 +0100 [thread overview]
Message-ID: <m34messdvo.fsf@gnus.org> (raw)
In-Reply-To: <87d1tg8rap.fsf@gnu.org> (Mike Gerwitz's message of "Tue, 05 Jan 2016 01:38:06 -0500")
Mike Gerwitz <mtg@gnu.org> writes:
> Personally, I prefer not to rely on bandages for my crypto.
It is, of course, up to you what you do for yourself.
What we're discussing is what the defaults should be in Emacs. Issuing
warnings to users about something that isn't (yet) a probable issue is a
disservice to our users. If they feel that these security mechanisms
get in the way of getting stuff done, they will, of course, just disable
those mechanisms altogether.
Which is why I asked to statistics of SHA-1 certificates in use today.
The newest one I could find was from April 2015, and at that point 20%
of Alexa Top 1000 web sites were using SHA-1 certificates. If that's
still the case, it's way more than is reasonable to warn our users
about.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-01-05 7:07 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
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 [this message]
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=m34messdvo.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=mtg@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.