From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/2328 Path: news.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.user Subject: Re: Bad PGP signatures due to MIME encoding (?) Date: Sat, 19 Apr 2003 14:49:47 +0200 Message-ID: References: <87istd7s2v.fsf@rpi.edu> <87vfxc9dlb.fsf@rpi.edu> <87lly7algz.fsf@rpi.edu> <87he8vf801.fsf@rpi.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138668798 14756 80.91.229.2 (31 Jan 2006 00:53:18 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:53:18 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:30:31 2006 Original-Path: quimby.gnus.org!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: fnatte.nada.kth.se Original-X-Trace: quimby.gnus.org 1050756773 9620 130.237.226.103 (19 Apr 2003 12:52:53 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 19 Apr 2003 12:52:53 GMT User-Agent: Gnus/5.090019 (Oort Gnus v0.19) Emacs/21.3.50 (gnu/linux) X-Face: $uE40g26bSBz:7_i5d,,_~>1,7\~848A:jNZ5WYBRjD@MurE}fc-lA3d@Y}ffA2Lo)W2j-/ |tx$A=HgsJ#kX5+Z%vk=?i>2^a=bVAj|Jd]^_xXbWcd6+I=\bHq{?'7-k%zp'p Marshall T. Vandegrift writes: > Simon Josefsson writes: > >> No idea, people complain about it from time to time. I refuse to >> enable the key phrase cache or gpg-agent so that I'm reminded that the >> problem is still there, in the hope that I get annoyed enough to >> actually investigate it some time. Not yet, though. > > Ooh... Yummy. So I investigated, sent around a bazillion test > messages to myself, and learned more features of the elisp debuggers > along the way. > > It looks like the cause is that `message-send' calls > `message-send-mail' or `message-send-news' (as appropriate), which > translates any mml in the message into actual MIME parts. If there's > a `Gcc' header, then `gnus-inews-do-gcc' eventually gets called, but > on the original message, so it gets to turn around and do all the > complicated mml-->MIME processing all over again, including PGP > signature generation. > > I don't know nearly enough about the Gnus internals to even begin > suggesting how to fix this, but it seems like there should be a Better > Way... Thanks for the analysis. I think one complication in solving this is when an article is both mailed and posted (to news). Depending on the destination, the body might end up being encoded differently, so it is unclear where to invoke the PGP signing. The same applies to GCC -- what encodings are appropriate for mail or news might not be appropriate for a GCC. I'm also not sure what a good solution would be. Perhaps simply explaining the problem is enough, then users can understand what is going on. In mail, the user can add a BCC to get a copy of the message as it really was sent. There should probably be a feature that inhibits PGP/SMIME for GCC. There is gnus-gcc-externalize-attachments now, that does roughly the same but for attachments. Maybe a gnus-gcc-inhibit-security would be useful.