From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] integrity of stage files
Date: Sat, 08 Oct 2011 16:39:40 -0700 [thread overview]
Message-ID: <4E90DF3C.8030307@gentoo.org> (raw)
In-Reply-To: <robbat2-20111008T223252-434133119Z@orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
On 10/8/11 3:43 PM, Robin H. Johnson wrote:
>> 1. Why are we using _only_ MD5 and SHA1 as the checksums? Shouldn't we
>> be using something stronger?
> Fixed in Catalyst now.
> http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=42b4f6608682cf03954918ecce7923330a1656fe
> So when the stagebuilders update their Catalyst, they will be generated
> with newer hashes.
Thank you for a quick reaction, but maybe in one aspect it was too
quick:
<http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=5>
tells people to use md5sum, and the patch above _removes_ md5 sum, which
means the Handbook instructions now won't work.
Suggested course of action:
1. Please re-add md5 sum.
2. File a bug to modify the handbook to verify sha sum instead.
3. Then remove the checksum.
>> 2. I noticed the checksums are signed (.asc files). With what key are
>> they signed? How is that key handled, and how to ensure people use the
>> right key when verifying the signature?
> Documented here:
> http://www.gentoo.org/proj/en/releng/
Ah, I just forgot about that page. Okay, so can we also update the
Handbook to include GPG signature checking?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2011-10-08 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 21:45 [gentoo-dev] integrity of stage files "Paweł Hajdan, Jr."
2011-10-08 22:43 ` Robin H. Johnson
2011-10-08 23:39 ` "Paweł Hajdan, Jr." [this message]
2011-10-09 0:01 ` Robin H. Johnson
2011-10-09 0:41 ` "Paweł Hajdan, Jr."
2011-10-09 0:44 ` Alec Warner
2011-10-09 0:51 ` Robin H. Johnson
2011-10-09 0:21 ` Matt Turner
2011-10-09 0:31 ` Robin H. Johnson
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=4E90DF3C.8030307@gentoo.org \
--to=phajdan.jr@gentoo.org \
--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