From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP59 - Manifest2 hashes
Date: Mon, 1 Feb 2010 02:23:42 -0600 [thread overview]
Message-ID: <eafa4c131002010023g55298f09q3978fec1a014ac74@mail.gmail.com> (raw)
In-Reply-To: <robbat2-20100131T094902-902405888Z@orbis-terrarum.net>
On Sun, Jan 31, 2010 at 3:57 AM, Robin H. Johnson <robbat2@gentoo.org> wrote:
<snip>
>
> The SHA512 algorithm is available in Python 2.5, which has been a
> dependency of Portage since approximately Python 2.1.6.13.
<snip>
I hate to nitpick, but I believe you meant Portage in that line.
However, great work on this GLEP, you've put forth some good solid
research into it.
I do hope that we don't intend on settling on SHA512 as the end all
solution as well. We should retain a method for bumping the hashing
algorithm used when the SHA-3 family becomes available.
--
Doug Goldstein
next prev parent reply other threads:[~2010-02-01 8:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 9:20 [gentoo-dev] Tree-signing GLEPs update Robin H. Johnson
2010-01-31 9:48 ` [gentoo-dev] GLEP58 - MetaManifest Robin H. Johnson
2010-02-02 6:27 ` Denis Dupeyron
2010-02-02 7:35 ` Robin H. Johnson
2010-01-31 9:57 ` [gentoo-dev] GLEP59 - Manifest2 hashes Robin H. Johnson
2010-02-01 5:05 ` Robin H. Johnson
2010-02-01 8:23 ` Doug Goldstein [this message]
2010-02-02 6:06 ` Denis Dupeyron
2010-02-04 2:57 ` Robin H. Johnson
2010-02-02 6:09 ` Robin H. Johnson
2010-01-31 10:01 ` [gentoo-dev] GLEP60 - Manifest2 filetypes Robin H. Johnson
2010-01-31 10:04 ` [gentoo-dev] GLEP61 - Manifest2 compression Robin H. Johnson
2010-02-08 1:02 ` Brian Harring
2010-02-08 5:23 ` Robin H. Johnson
2010-02-08 5:50 ` Brian Harring
2010-01-31 10:11 ` [gentoo-dev] Tree-signing GLEPS review notes 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=eafa4c131002010023g55298f09q3978fec1a014ac74@mail.gmail.com \
--to=cardoe@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