[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Import of libgcrypt 1.4.4 ciphers (was: Re: [PATCH] Cryptography)
From: |
Robert Millan |
Subject: |
Import of libgcrypt 1.4.4 ciphers (was: Re: [PATCH] Cryptography) |
Date: |
Mon, 16 Nov 2009 22:16:15 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Mon, Nov 16, 2009 at 09:20:00PM +0100, Vladimir 'phcoder' Serbinenko wrote:
> Robert Millan wrote:
> >
> > Ok. Then in principle we wouldn't contemplate resyncing this file, right?
> Unless there will be a cryptographic or legal issue, no. PBKDF2 is a
> static standard
Alright.
> and ChangeLog doesn't mention anything that would result in a different
> import, except of the currently unused public-key cryptography files
> (and which will require adaptations in import_gcry.py to be handled) and
> unused files md.c/cipher.c included in import for reference.
> So I recommend importing 1.4.4
I imported ciphers from 1.4.4 in this branch:
sftp://bzr.savannah.gnu.org/srv/bzr/grub/people/robertmh/libgcrypt
also, I integrated your import_gcry.py script with autogen.sh. This way
auto-generated files don't have to be hosted in our repository. If in
the future original libgcrypt files need modification, this can be committed
directly in lib/libgcrypt (provided that we coordinate with libgcrypt
maintainers to have those changes merged back, of course).
When you have confirmed that this seems correct to you, I'll write a
ChangeLog entry and merge in trunk.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
Re: [PATCH] Cryptography, Felix Zielcke, 2009/11/16
Re: [PATCH] Cryptography, Robert Millan, 2009/11/17