Your message dated Sat, 22 Dec 2007 07:47:03 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#428635: fixed in gnupg2 2.0.8-1 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message --------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 know that while it is generally not advised to have dsa keys larger than 1024 bits since they are not universally acceptable, however, it is an option that can be enabled, and therefore should work as expected. gpg (GnuPG) 2.0.4; Copyright (C) 2007 Free Software Foundation, Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the file COPYING for details. Please select what kind of key you want: (1) DSA and Elgamal (default) (2) DSA (sign only) (5) RSA (sign only) Your selection? 1 DSA keys may be between 1024 and 3072 bits long. What keysize do you want? (1024) 3072 Requested keysize is 3072 bits ELG keys may be between 1024 and 4096 bits long. What keysize do you want? (2048) 4096 Requested keysize is 4096 bits Please specify how long the key should be valid. 0 = key does not expire <n> = key expires in n days <n>w = key expires in n weeks <n>m = key expires in n months <n>y = key expires in n years Key is valid for? (0) 0 Key does not expire at all Is this correct? (y/N) y You need a user ID to identify your key; the software constructs the user ID from the Real Name, Comment and Email Address in this form: "Heinrich Heine (Der Dichter) <[EMAIL PROTECTED]>" Real name: woaosoaoososas Email address: [EMAIL PROTECTED] Comment: You selected this USER-ID: "woaosoaoososas <[EMAIL PROTECTED]>" Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O You need a Passphrase to protect your secret key. We need to generate a lot of random bytes. It is a good idea to perform some other action (type on the keyboard, move the mouse, utilize the disks) during the prime generation; this gives the random number generator a better chance to gain enough entropy. gpg: WARNING: some OpenPGP programs can't handle a DSA key with this digest size gpg2: dsa.c:187: generate: Assertion `nbits >= 512 && nbits <= 1024' failed. Aborted Thanks, Huy - --- System information. --- Architecture: i386 Kernel: Linux 2.6.20 Debian Release: lenny/sid 990 unstable ftp.de.debian.org 500 testing security.debian.org 500 testing ftp.de.debian.org 500 stable security.debian.org 1 experimental ftp.de.debian.org - --- Package information. --- Depends (Version) | Installed ===============================-+-============== libbz2-1.0 | 1.0.3-7 libc6 (>= 2.5-5) | 2.5-10 libgcrypt11 (>= 1.2.2) | 1.2.4-2 libgpg-error0 (>= 1.4) | 1.4-2 libksba8 (>= 1.0.0) | 1.0.1-2 libldap2 (>= 2.1.17-1) | 2.1.30-13.4 libreadline5 (>= 5.2) | 5.2-3 zlib1g (>= 1:1.2.1) | 1:1.2.3-15 - -- Key ID = 0xE024A6F3 Key fingerprint = C9A1 2E1E 1E10 6514 2E7D 8934 08C6 B43F E024 A6F3 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (GNU/Linux) iQIVAwUBRm90uZfhWeS24kpvAQob/Q/9EphIFZY/lfPU9Tlldqo3KZC5ijF5r3QZ vET1yMpfY5bn7SVUNdH91KQ4uVWZ2mGVUvUic6yl/Tcx9oGMiiEg0dxe7bx1EzXl BZDZAwBAvtq0cP4JrqKcFM3Qqxn5RDhEHmh+G8EMFII4goJVxSlFAQT4WWSRepoc leEZoN/59p51J+u9ghJ9RTqepUFdLFrnkg4QbJEHDNdIlyhXqPaMAaHxStiBjLI+ pDEnfFE698jMAiwcx3/k1TqceWILeAGIfj7M3XXZAi4luTKYSrgnzs2Jykd7VezO j0WsvTruZhFB6SDfEh/BssWQQWfB3nWiCjl0qFY0yrOOfjJBAKMhiM3INT5VRRLN cg0vZwikqKN5nzM9nA4xW94OPV220ooPzdociyONmvO7yZtxsPPh3PTXtqwwBWQa /b3sRmsKPIzZd/f8M3nLd+jqGLxTIUrBCfXDhEBa+JXhxNFMOXBhWD4EfJ4Xl5JS qeMfYj1ae6+TXigkxd0BLzDzr5zl2+6nDQsQE0iW3QjcLgx76twV6MB5ud09xcAg pT0cyyXLX6q8U64i2lJtzVcZbB6/bh1Wn3D+06nYDFK+jJkB0xPYLnpMF++nEttD x1PVXlFUwNom9i7/FIZCYFyDH12CLvkVAkxrfwCeb90aSMq9MjbEMo9PcxlBDO/t IT4kMc8HuJk= =MZof -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---Source: gnupg2 Source-Version: 2.0.8-1 We believe that the bug you reported is fixed in the latest version of gnupg2, which is due to be installed in the Debian FTP archive: gnupg-agent_2.0.8-1_amd64.deb to pool/main/g/gnupg2/gnupg-agent_2.0.8-1_amd64.deb gnupg2_2.0.8-1.diff.gz to pool/main/g/gnupg2/gnupg2_2.0.8-1.diff.gz gnupg2_2.0.8-1.dsc to pool/main/g/gnupg2/gnupg2_2.0.8-1.dsc gnupg2_2.0.8-1_amd64.deb to pool/main/g/gnupg2/gnupg2_2.0.8-1_amd64.deb gnupg2_2.0.8.orig.tar.gz to pool/main/g/gnupg2/gnupg2_2.0.8.orig.tar.gz gpgsm_2.0.8-1_amd64.deb to pool/main/g/gnupg2/gpgsm_2.0.8-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eric Dorland <[EMAIL PROTECTED]> (supplier of updated gnupg2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sat, 22 Dec 2007 02:06:42 -0500 Source: gnupg2 Binary: gnupg2 gpgsm gnupg-agent Architecture: source amd64 Version: 2.0.8-1 Distribution: unstable Urgency: low Maintainer: Eric Dorland <[EMAIL PROTECTED]> Changed-By: Eric Dorland <[EMAIL PROTECTED]> Description: gnupg-agent - GNU privacy guard - password agent gnupg2 - GNU privacy guard - a free PGP replacement gpgsm - GNU privacy guard - S/MIME version Closes: 428635 456467 Changes: gnupg2 (2.0.8-1) unstable; urgency=low . * New upstream release. (Closes: #428635) * debian/watch: Use passive ftp, ftp.gnupg.org doesn't seem happy otherwise. (Closes: #456467) * debian/control: - Requires libassuan >= 1.0.4 now. - Remove the XS- prefix from the Vcs-* headers. - Add Homepage header. - Upgrade Standards-Version to 3.7.3.0. - Make gnupg2 optional rather than extra. - Remove unnecessary conflict on suidmanager. Files: 21ec723181f07b781936ecc5065239a0 970 utils optional gnupg2_2.0.8-1.dsc 3d87a0e8fe7d1ed9b10fa94a022feab8 5118599 utils optional gnupg2_2.0.8.orig.tar.gz fc237256d900b07962b2c2a8d78f9f9b 38106 utils optional gnupg2_2.0.8-1.diff.gz 56fb52777a92cf6a24f40d0e45155ba8 309254 utils optional gnupg-agent_2.0.8-1_amd64.deb ee36a6993cc4037f849dc8ae0cde19ad 451976 utils optional gpgsm_2.0.8-1_amd64.deb 20d335d0e82e8bad6b0e2b265a8ae978 2120960 utils optional gnupg2_2.0.8-1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHbL2gYemOzxbZcMYRAn22AJ92SHZ0ZWShmgVKpbEXIMlL7L87iwCeK4DL NQXHrkiKF83F3L6zQfAeeCM= =PHBy -----END PGP SIGNATURE-----
--- End Message ---
