From: Zac Medico <zmedico@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, 02 Oct 2011 14:10:09 -0700 [thread overview]
Message-ID: <4E88D331.8060700@gentoo.org> (raw)
In-Reply-To: <robbat2-20111002T205023-994013243Z@orbis-terrarum.net>
On 10/02/2011 01:54 PM, Robin H. Johnson wrote:
> On Sun, Oct 02, 2011 at 01:39:41PM -0700, Zac Medico 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:
> Did you mean profiles/layout.conf? I just want to make sure no scripts
> that pull from CVS and expect that dir to not exist don't break.
No, it's metadata/layout.conf. I didn't choose the location. We actually
inherited it from paludis about 1.5 years ago:
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=f16aee82cefa95e9903fa46f448d30f6d4350f64
We're also using it to control thin-manifest support, among other things
now:
https://bugs.gentoo.org/show_bug.cgi?id=333691
>> manifest2-sha1 = true
>> manifest2-whirlpool = false
> Bikeshedding slightly, but can we figure something like a list or dict
> instead? (Also gives us a chance to make the required hashes a list).
> manifest2-hashes = ['SHA1', 'SHA256', 'RMD160']
Well, booleans are simpler. Also, note that I designed them to be
removed from layout.conf eventually, which means that we will accumulate
less bloat in layout.conf over time.
>> 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.
> Sounds good to me. Hopefully I'll have more of the MetaManifest
> prototype code in the next few days to go live around the same time.
I'll see if I can get a layout.conf patch done today.
--
Thanks,
Zac
next prev parent reply other threads:[~2011-10-02 21:10 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
2011-10-02 20:54 ` Robin H. Johnson
2011-10-02 21:10 ` Zac Medico [this message]
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=4E88D331.8060700@gentoo.org \
--to=zmedico@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