From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Mike Gerwitz <mtg@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The SHA1 sunset
Date: Mon, 04 Jan 2016 23:14:06 +0100 [thread overview]
Message-ID: <m3y4c5vvpt.fsf@gnus.org> (raw)
In-Reply-To: <87si2eayc5.fsf@gnu.org> (Mike Gerwitz's message of "Sun, 03 Jan 2016 21:10:50 -0500")
Mike Gerwitz <mtg@gnu.org> writes:
> The date that browsers implement warnings is arbitrary; this is still
> certainly "a thing".
>
> https://sites.google.com/site/itstheshappening/
I'm not sure why you're linking to that site?
The question isn't whether the NSA are able to do SHA-1 collisions
(which I think everybody assumes that they can, albeit expensively), but
whether they can create certificates. The jury is out on that one, and
many people think that it's not a thing (yet) (with certificates with
the recommended entropy in serial numbers and dates).
https://blog.cloudflare.com/why-its-harder-to-forge-a-sha-1-certificate-than-it-is-to-find-a-sha-1-collision/
> Such a warning will not be bogus, and it would be a service to warn
> users even if others don't.
It will almost certainly be bogus (now). Next year, perhaps not.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-01-04 22:14 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 [this message]
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=m3y4c5vvpt.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.