On Tue, 11 Dec 2007 20:03, [EMAIL PROTECTED] said:
> Upgrading to libgcrypt11 1.4.0 generates a different error. However
> I think this one is really a gnupg2 error, not a gcrypt one.
Alright. Thanks for reminding that I need to add support for DSA-2.
Will do this tomorrow so that we can get 2.0
On 2007-12-11 Simon Josefsson <[EMAIL PROTECTED]> wrote:
> I believe the problem is because libgcrypt is too old and doesn't
> support DSA2.
> Libgcrypt 1.4.0 do support DSA2. Once 1.4.0 has been installed in
> Debian, I think this problem should be solved in the gnupg2 package by
> adding a 'lib
I believe the problem is because libgcrypt is too old and doesn't
support DSA2.
Libgcrypt 1.4.0 do support DSA2. Once 1.4.0 has been installed in
Debian, I think this problem should be solved in the gnupg2 package by
adding a 'libgcrypt (>= 1.4.0)' dependency.
/Simon
--
To UNSUBSCRIBE, email
reassign 428635 libgcrypt11
severity 428635 normal
thanks
The assertion generated there is actually from libgcrypt, so your beef
is with them :)
* Huy ([EMAIL PROTECTED]) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Package: gnupg2
> Version: 2.0.4-1
> Severity: important
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: gnupg2
Version: 2.0.4-1
Severity: important
Hello,
Gnupg2 gives out the following error as it tries to create dsa2 keys,
that is keys with size larger than 1024 bits, even though the
enable-dsa2 was already put in $HOME/.gnupg/gpg.conf.
I
5 matches
Mail list logo
