Your message dated Fri, 8 May 2009 09:59:02 +0200 (CEST)
with message-id <[email protected]>
and subject line Bug#337165: Unattended key generation breaks with "Ohhhh
jeeee: ... this is a bug"
has caused the Debian Bug report #337165,
regarding gnupg: Unattended key generation breaks with "Ohhhh jeeee: ... this
is a bug" when using unknown algorithm
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
337165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=337165
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 1.4.2-2
Severity: normal
I tried to create a key in an unattended way using this file:
| Key-Type: DSA
| Key-Length: 1024
| Subkey-Type: ElGamal
| Subkey-Length: 2048
| Name-Real: Backups for host foobar
| Name-Email: [email protected]
| Expire-Date: 2y
| Passphrase: foo
Which made GnuPG die with an Ohhh jee:
} wea...@galaxy:~/tmp/foo$ gpg --batch --gen-key < ./keygen
} gpg: WARNING: unsafe permissions on homedir `.'
}
+++++++++++++++.+++++++++++++++++++++++++++++++++++++++++++++.+++++.+++++++++++++++.+++++.+++++++++++++++++++++++++++++++++++++++++++++>+++++..+++++<+++++....>+++++.................................................................................................................+++++
}
} gpg: Ohhhh jeeee: ... this is a bug (keygen.c:1872:do_create)
} secmem usage: 1856/3328 bytes in 7/11 blocks of pool 3488/32768
} zsh: abort gpg --batch --gen-key < ./keygen
If I use a proper algorithm name (like ELG-E) instead of the wrong
ElGamal everything is fine, but the error handling could be better :)
--
Peter
--- End Message ---
--- Begin Message ---
GnuPG now exits with a proper error message, so I assume, this bug has been
fixed. Closing then.
Regards, Daniel
--- End Message ---
