From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 37420@debbugs.gnu.org
Subject: bug#37420: [PATCH] Recommend against SHA-1 for security-related applications
Date: Tue, 17 Sep 2019 14:08:51 +0200 [thread overview]
Message-ID: <CADwFkmk7-Y6rjWbnSeeyW+g=QzMQ-=nhTQ+meOHhmdLaFnRM9Q@mail.gmail.com> (raw)
In-Reply-To: <83a7b3w34h.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> > > Should we perhaps do something to help those who know this under the
> > > name "SHA1"?
> >
> > Is there any risk that some users believe that these would be two
> > different algorithms? My guess would be no, but I might be wrong.
>
> I have no idea, but I personally didn't even know SHA1 has another
> name, let alone a more "official" one.
This is the spelling in RFC 3174: https://tools.ietf.org/html/rfc3174
Perhaps SHA1 is just a common typo?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-09-17 12:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 8:53 bug#37420: [PATCH] Recommend against SHA-1 for security-related applications Stefan Kangas
2019-09-16 11:21 ` Lars Ingebrigtsen
2019-09-16 20:29 ` Stefan Kangas
2019-09-16 20:34 ` Lars Ingebrigtsen
2019-09-16 21:50 ` Stefan Kangas
2019-09-16 22:25 ` Lars Ingebrigtsen
2019-09-17 9:17 ` Stefan Kangas
2019-09-17 6:05 ` Eli Zaretskii
2019-09-17 13:37 ` Robert Pluim
2019-09-28 10:19 ` Stefan Kangas
2019-09-28 19:55 ` Lars Ingebrigtsen
2019-10-04 15:33 ` Stefan Kangas
2019-09-17 5:50 ` Eli Zaretskii
2019-09-17 9:09 ` Stefan Kangas
2019-09-17 11:53 ` Eli Zaretskii
2019-09-17 12:08 ` Stefan Kangas [this message]
2019-09-17 12:14 ` Stefan Kangas
2019-09-20 18:50 ` Stefan Kangas
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='CADwFkmk7-Y6rjWbnSeeyW+g=QzMQ-=nhTQ+meOHhmdLaFnRM9Q@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=37420@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).