From: Mark H Weaver <mhw@netris.org>
To: Mark Rijckenberg <markrijckenberg@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: SHA-1 vs SHA256 + public key
Date: Tue, 23 May 2017 02:37:31 -0400 [thread overview]
Message-ID: <87bmqkt6xg.fsf@netris.org> (raw)
In-Reply-To: <87fufwtbag.fsf@netris.org> (Mark H. Weaver's message of "Tue, 23 May 2017 01:03:19 -0400")
I wrote:
> The hashes included in the announcement are not able to provide secure
> authentication, regardless of what hash function is used, because the
> announcement itself might have been modified
I forgot that the announcement itself was signed, which invalidates much
of what I wrote earlier. Sorry for the noise.
I agree that we should include stronger hashes in the announcement.
Mark
next prev parent reply other threads:[~2017-05-23 6:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 18:23 SHA-1 vs SHA256 + public key Mark Rijckenberg
2017-05-23 5:03 ` Mark H Weaver
2017-05-23 6:37 ` Mark H Weaver [this message]
2017-05-23 20:53 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmqkt6xg.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=markrijckenberg@gmail.com \
/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/guix.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).