public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] integrity of stage files
Date: Sat, 8 Oct 2011 20:21:44 -0400	[thread overview]
Message-ID: <CAEdQ38E-dDbgUkNzhuCSp9Sgzv+QaJUCAQ3pbUrHEqJPeu03kg@mail.gmail.com> (raw)
In-Reply-To: <robbat2-20111008T223252-434133119Z@orbis-terrarum.net>

On Sat, Oct 8, 2011 at 6:43 PM, Robin H. Johnson <robbat2@gentoo.org> wrote:
> On Sat, Oct 08, 2011 at 02:45:02PM -0700, "Paweł Hajdan, Jr." wrote:
>> I checked
>> <http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=5>
>> and the Handbook only mentions validating MD5 checksums.
>>
>> There are two possible issues:
>>
>> 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.

Well, almost.

The changes you made are in the master branch (for catalyst-3), but
since catalyst-3 isn't really going anywhere fast, you should
cherry-pick your patches back to the catalyst_2 branch so they'll be
available in the next 2.0.6.919 release.

Matt



  parent reply	other threads:[~2011-10-09  0:22 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."
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 [this message]
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=CAEdQ38E-dDbgUkNzhuCSp9Sgzv+QaJUCAQ3pbUrHEqJPeu03kg@mail.gmail.com \
    --to=mattst88@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