<<< Date Index >>>     <<< Thread Index >>>

GPG and good signature (mis?)behaviour



Hi mutters,

I'm getting this strange behaviour when I try to verify the integrity
of a message with mime type multipart/signed and signed with PGP.

In most cases it works just fine, but in some cases I get something
as:

[-- PGP output follows (current time: Tue 01 May 2007 03:50:24 PM CEST) --]
gpg: Signature made Tue 01 May 2007 03:34:27 PM CEST using DSA key ID XXXXXXXX
gpg: Good signature from "xxxxxx xxxxxxx <xxxxxxxxxxxxxxxxxxxx>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: xxxx xxxx xxxx xxxx xxxx  xxxx xxxx xxxx xxxx xxxx
[-- End of PGP output --]

So the signature should be a good one, but the flag in the index
remains "s" rather than "S" (correctly signed). As I said, this
doesn't work as expected just in few cases.

This is my crypto setting:

# %f: message file
# %s: signature file
# %a: pgp_sign_as value
set pgp_decode_command="gpg %?p? --passphrase-fd 0? --no-verbose --batch 
--output - %f"
set pgp_verify_command="gpg --no-verbose --batch --output - --verify %s %f"
set pgp_decrypt_command="gpg --passphrase-fd 0 --no-verbose --batch --output - 
%f"
set pgp_sign_command="gpg --no-verbose --batch --output - --passphrase-fd 0 
--armor --detach-sign --textmode %?a?-u %a? %f"
set pgp_clearsign_command="gpg --no-verbose --batch --output - --passphrase-fd 
0 --armor --textmode --clearsign %?a?-u %a? %f"
set pgp_encrypt_only_command="pgpewrap gpg --batch --quiet --no-verbose 
--output - --encrypt --textmode --armor --always-trust --encrypt-to 0xC9C40C31 
-- -r %r -- %f"
set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 --batch --quiet 
--no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor 
--always-trust --encrypt-to 0xC9C40C31 -- -r %r -- %f"
set pgp_import_command="gpg --no-verbose --import -v %f"
set pgp_export_command="gpg --no-verbose --export --armor %r"
set pgp_verify_key_command="gpg --no-verbose --batch --fingerprint --check-sigs 
%r"
set pgp_list_pubring_command="gpg --no-verbose --batch --with-colons 
--list-keys %r" 
set pgp_list_secring_command="gpg --no-verbose --batch --with-colons 
--list-secret-keys %r" 

# a regexp: if that matches the mutt output from pgp_verify_command then the 
message is considered verified
# I'm not sure this is necessary, since gpg already exit with an useful exit 
code of 0 in case
# of success
set pgp_good_sign="^gpg: Good signature from"
#set pgp_check_exit=no

I'm using mutt 1.5.13. 

Can you explain this behaviour? Is it maybe a mutt bug?
Thanks in advance for any help.
-- 
mutt tip #1
set resolve=yes
get mutt cursor move to the next message when an action is performed (most 
contexts)