> The patch fixes the crash, however, the message output when such > messages are viewed doesn't actually help verify the problematic > emails. I have moved ~/.gnupg/pubring.gpg* aside and the message still > appears - the key needs to be reimported to allow verification. I > suggest that the message is updated to indicate this (although the > message is already quite long). > > Instead of: > The signature can't be checked - End of file. Removing > left-over ~/.gnupg/pubring.gpg might solve the > problem if you have installed gpg-v21 > > Possibly: > The signature can't be checked. If you have installed > gpg-v21, remove ~/.gnupg/pubring.gpg and reimport the key. > > Alternatively, claws-mail could check for the existence of gpgv-21 (by > finding pubring.kbx) and skip that part of the message. > > My preference would be for the crash to be fixed first and the message > improvement later. > > Further, my public key also had to be re-imported before claws could > sign this email.
OK, the string output by this patch is actually quite pointless. Yes, moving pubring.gpg and reimporting the key allows verification but importing the key simply regenerates pubring.gpg too - the same size as before. So removing the file has no effect at all. The key simply needs to be reimported. > Possibly: > The signature can't be checked. If you have installed > gpg-v21, remove ~/.gnupg/pubring.gpg and reimport the key. The signature can't be checked. If you have installed gpg-v21, the key needs to be reimported. > Alternatively, claws-mail could check for the existence of gpgv-21 (by > finding pubring.kbx) and skip that part of the message. ... The signature can't be checked. The key needs to be reimported for compatibility your updated gpg. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
pgpd9_m2VDTqq.pgp
Description: OpenPGP digital signature
