From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH 3/4] Manifest2 hash backend provider: mhash
Date: Fri, 30 Sep 2011 22:51:03 +0000 [thread overview]
Message-ID: <robbat2-20110930T223759-026289809Z@orbis-terrarum.net> (raw)
In-Reply-To: <1317346062-10156-4-git-send-email-robbat2@gentoo.org>
On Fri, Sep 30, 2011 at 01:27:41AM +0000, Robin H. Johnson wrote:
> Offer mhash as a provider for Manifest2 hash generation and validation.
> This is important as none of pycrypto/hashlib/fchksum offer an
> accelerated Whirlpool implementaiton. Additionally, the mhash
> implementation is accelerated and ships with a rigorious testsuite.
ferringb has pointed out that mhash holds the GIL lock, and that hashlib
does support whirlpool (despite the docs not mentioning it).
This portion might end up dropped then.
--
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail : robbat2@gentoo.org
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
next prev parent reply other threads:[~2011-09-30 22:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 1:27 [gentoo-portage-dev] GLEP59: Manifest2 hash types implementation Robin H. Johnson
2011-09-30 1:27 ` [gentoo-portage-dev] [PATCH 1/4] Manifest2 hash: Whirlpool Robin H. Johnson
2011-10-01 18:08 ` Mike Frysinger
2011-10-01 20:38 ` Alec Warner
2011-10-01 22:25 ` Robin H. Johnson
2011-09-30 1:27 ` [gentoo-portage-dev] [PATCH 2/4] Manifest2 hash: SHA512 Robin H. Johnson
2011-09-30 1:27 ` [gentoo-portage-dev] [PATCH 3/4] Manifest2 hash backend provider: mhash Robin H. Johnson
2011-09-30 22:51 ` Robin H. Johnson [this message]
2011-09-30 1:27 ` [gentoo-portage-dev] [PATCH 4/4] GLEP59: Change live Manifest2 hashes to SHA256, SHA512, WHIRLPOOL Robin H. Johnson
2011-09-30 17:19 ` [gentoo-portage-dev] GLEP59: Manifest2 hash types implementation James Cloos
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=robbat2-20110930T223759-026289809Z@orbis-terrarum.net \
--to=robbat2@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