Debian Bug report logs - #118052
tin: no gpg ouput with bad signature

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: [email protected]

To: [email protected]

Subject: tin: no gpg ouput with bad signature

Date: Fri, 02 Nov 2001 18:34:07 +0100

Package: tin
Version: 1:1.5.8-7.pit.pot.3
Severity: important

I use version 1.5.8-8 compiled on potato. When checking a bad signature
with gpg there is a "command failed: <gpg-cmd>" output instead of the gpg
output "BAD signature <...>".

I think gpg exits with 1 if at least one sig was bad and that this is
interpreted as an execution error. As the whole sense in using gpg is
detection of *bad* sigs, the output should unmistakably report that.

Regards,
Jens

-- System Information
Debian Release: 2.2
Kernel Version: Linux pitje 2.4.13 #1 Wed Oct 24 14:18:46 CEST 2001 i586 unknown

Versions of the packages tin depends on:
ii  debconf        0.2.80.17      Debian configuration management system
ii  libc6          2.1.3-13       GNU C Library: Shared libraries and Timezone
ii  libncurses5    5.0-6.0potato1 Shared libraries for terminal handling
ii  libpcre2       2.08-1         Philip Hazel's Perl Compatible Regular Expre
ii  metamail       2.7-34         An implementation of MIME.

Send a report that this bug log contains spam.