From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] SHA256 digest issues
Date: Thu, 27 Apr 2006 12:21:35 +0100 [thread overview]
Message-ID: <20060427122135.665ef0fb@snowdrop.home> (raw)
In-Reply-To: <20060427105002.GA7582@cyclops.localdomain>
On Thu, 27 Apr 2006 12:50:02 +0200 Marien Zwart <marienz@gentoo.org>
wrote:
| We (portage project) are fixing known broken Manifests/digests. If you
| come across any broken SHA256 digests feel free to fix them though:
| the package is basically unusable with ~arch portage until it is
| fixed, and fixing it twice does not really hurt :)
If you're looking to avoid downloading too much... All source tarballs
whose file size (mod 64) is 55 are the ones affected, which would
suggest that somewhere very roughly in the region of one package in
sixty four with SHA256 digests is h0rked.
There's a good testsuite which would have caught this at [1].
[1]: http://csrc.nist.gov/cryptval/shs.htm
--
Ciaran McCreesh
Mail : ciaran dot mccreesh at blueyonder.co.uk
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2006-04-27 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 10:50 [gentoo-dev] SHA256 digest issues Marien Zwart
2006-04-27 11:21 ` Ciaran McCreesh [this message]
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=20060427122135.665ef0fb@snowdrop.home \
--to=ciaran.mccreesh@blueyonder.co.uk \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox