also sprach Derek Martin <inva...@pizzashack.org> [2009.11.28.0314 +0100]: > I have pgp_auto_decode set, and additionally I unset it and manually > executed check-traditional-pgp, and I saw the above text in all cases. > So unless I misunderstood you, it seems my Mutt behaves differently > from yours...
Indeed, and I take curiosity in that. More below... > But besides that, check-traditional-pgp is not intended to work > with MIME messages... (I know) > 3.153. pgp_auto_decode [...] > So, you may not like the behavior, but it's not a bug. The > solution, as already noted, is to unset pgp_auto_decode. It's > neither appropriate nor required for MIME-based PGP mails, as mutt > already does the right thing there without it if the messages are > marked properly. The option is probably obsolete or headed there, > and probably should not be set by default. I think the actual bug I am looking at is not with pgp_auto_decode, since, as far as I understand, it only calls <check-traditional-pgp> on *every* message. The problem is with <check-traditional-pgp>. If you have a message that is: unsigned content -- begin signed -- signed content -- signature -- OSCNLKSknsc.. -- end signed -- unsigned content then <check-traditional-pgp> will feed all 7 lines to GPG, and GPG will swallow the first and the last lines. Either gnupg needs to learn to emit unsigned content, and visually distinguish signed from unsigned content, e.g unsigned content -- begin signed content -- signed content -- end signed content -- unsigned content or mutt needs to learn to only pass the signed content (along with the signature) to gnupg. I /think/ that the latter is the better solution, because mutt already uses visual markers to distinguish signed from unsigned content: [-- The following data is signed --] (that should be s/is/are/) and re-using output from gnupg and reformatting it (e.g. to appear bold) just seems a bit like a hack. Also, it makes no real sense to filter unsigned content through gnupg and expect it to return it verbatim, IMHO. I think <check-traditional-pgp> needs to learn to only pass to gnupg those parts of a message that are marked up as inline-signed, and put the output between the aforementioned visual markers. Everything else should be shown verbatim in the pager, and not passed to the gnupg tool for verification. Am I making sense? -- martin | http://madduck.net/ | http://two.sentenc.es/ a farmer is a man outstanding in his field. spamtraps: madduck.bo...@madduck.net
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
