From: Alec Warner <antarus@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [GLEP59v2 5/5] GLEP59: Change live Manifest2 hashes to SHA256, SHA512, WHIRLPOOL
Date: Sun, 2 Oct 2011 13:46:58 -0700 [thread overview]
Message-ID: <CAAr7Pr8zGY2VEf6bGkw4TbAdGGPDMjVthdMJX3YUqfjrqB_q6g@mail.gmail.com> (raw)
In-Reply-To: <4E88CC0D.6080702@gentoo.org>
On Sun, Oct 2, 2011 at 1:39 PM, Zac Medico <zmedico@gentoo.org> wrote:
> On 10/02/2011 05:46 AM, Robin H. Johnson wrote:
>> On Sat, Oct 01, 2011 at 09:40:13PM -0700, Zac Medico wrote:
>>> If we control these hashes via metadata/layout.conf, then we can toggle
>>> it atomically for all commiters. Otherwise, we'll have an annoying
>>> period of time where different committers are committing different sets
>>> of hashes, depending on their portage version.
>> How do you suggest doing it via layout.conf? I've kept SHA256 in both
>> sets for now, but if you could enforce new signatures including both
>> WHIRLPOOL and SHA256, that would be great.
>
> How about if we put something like this in
> gentoo-x86/metadata/layout.conf now:
Reminds me, I was going to do an analysis on -commit mails to track
portage versions; I'll do that now.
>
> manifest2-sha1 = true
> manifest2-whirlpool = false
>
> Then we'll patch portage so that by default it will disable SHA1 and
> enable WHIRLPOOL, and the above settings will override the defaults.
> After the patched portage is marked stable in a month or so, we'll send
> an announcement to gentoo-announce, and remove the above settings from
> layout.conf.
> --
> Thanks,
> Zac
>
>
next prev parent reply other threads:[~2011-10-02 20:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 7:40 [gentoo-portage-dev] [GLEP59v2 0/5] GLEP59: Manifest2 hash types Robin H. Johnson
2011-10-01 7:40 ` [gentoo-portage-dev] [GLEP59v2 1/5] Refactor RMD160 hashlib code for less-hardcoding Robin H. Johnson
2011-10-01 7:40 ` [gentoo-portage-dev] [GLEP59v2 2/5] Manifest2 hash: Whirlpool Robin H. Johnson
2011-10-01 9:41 ` Brian Harring
2011-10-02 6:15 ` Zac Medico
2011-10-01 7:40 ` [gentoo-portage-dev] [GLEP59v2 3/5] Manifest2 hash: SHA512 Robin H. Johnson
2011-10-01 7:40 ` [gentoo-portage-dev] [GLEP59v2 4/5] Manifest2 hash backend provider: mhash Robin H. Johnson
2011-10-01 7:40 ` [gentoo-portage-dev] [GLEP59v2 5/5] GLEP59: Change live Manifest2 hashes to SHA256, SHA512, WHIRLPOOL Robin H. Johnson
2011-10-02 4:40 ` Zac Medico
2011-10-02 6:14 ` Zac Medico
2011-10-02 12:46 ` Robin H. Johnson
2011-10-02 20:39 ` Zac Medico
2011-10-02 20:46 ` Alec Warner [this message]
2011-10-02 20:54 ` Robin H. Johnson
2011-10-02 21:10 ` Zac Medico
2011-10-02 23:22 ` Brian Harring
2011-10-03 0:21 ` Zac Medico
2011-10-03 9:48 ` Zac Medico
2011-10-03 11:43 ` Brian Harring
2011-10-03 14:18 ` Zac Medico
2011-10-05 18:07 ` [gentoo-portage-dev] [GLEP59v2 0/5] GLEP59: Manifest2 hash types Zac Medico
2011-10-05 18:24 ` 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=CAAr7Pr8zGY2VEf6bGkw4TbAdGGPDMjVthdMJX3YUqfjrqB_q6g@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-portage-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