From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/61690 Path: news.gmane.org!not-for-mail From: "Mark D. Baushke" Newsgroups: gmane.mail.mh-e.devel,gmane.emacs.gnus.general Subject: Re: Gnus 5.10.6 problems with PGP/MIME (test cases) Date: Tue, 17 Jan 2006 10:17:54 -0800 Message-ID: <85906.1137521874@juniper.net> References: <19643.1137028354@juniper.net> <26554.1137393402@juniper.net> <25107.1137439020@olgas.newt.com> <73630.1137440939@juniper.net> <31430.1137488443@juniper.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1137521976 29371 80.91.229.2 (17 Jan 2006 18:19:36 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 17 Jan 2006 18:19:36 +0000 (UTC) Cc: mh-e-devel@lists.sourceforge.net, ding@gnus.org Original-X-From: mh-e-devel-admin@lists.sourceforge.net Tue Jan 17 19:19:28 2006 Return-path: Envelope-to: gmmd-mh-e-devel@m.gmane.org Original-Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EyvQ6-0001SR-02 for gmmd-mh-e-devel@m.gmane.org; Tue, 17 Jan 2006 19:19:02 +0100 Original-Received: from sc8-sf-list1-b.sourceforge.net (sc8-sf-list1-b.sourceforge.net [10.3.1.7]) by sc8-sf-spam1.sourceforge.net (Postfix) with ESMTP id 6885D3357E; Tue, 17 Jan 2006 10:19:01 -0800 (PST) Original-Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92] helo=mail.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30) id 1EyvPL-0007n4-9U for mh-e-devel@lists.sourceforge.net; Tue, 17 Jan 2006 10:18:15 -0800 Original-Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by mail.sourceforge.net with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.44) id 1EyvPI-0007za-9v for mh-e-devel@lists.sourceforge.net; Tue, 17 Jan 2006 10:18:15 -0800 Original-Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id k0HII0553673; Tue, 17 Jan 2006 10:18:02 -0800 (PST) (envelope-from mdb@juniper.net) Original-Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k0HIHs594617; Tue, 17 Jan 2006 10:17:54 -0800 (PST) (envelope-from mdb@juniper.net) Original-To: Katsumi Yamaoka In-Reply-To: X-Mailer: MH-E 7.85+cvs; nmh 1.0.4; GNU Emacs 21.3.1 X-Face: #8D_6URD2G%vC.hzU, List-Id: Forum for the MH-E developers List-Post: List-Help: List-Subscribe: , List-Archive: X-Original-Date: Tue, 17 Jan 2006 10:17:54 -0800 Xref: news.gmane.org gmane.mail.mh-e.devel:11362 gmane.emacs.gnus.general:61690 Archived-At: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Katsumi, Katsumi Yamaoka writes: > >>>>> In <31430.1137488443@juniper.net> Mark D. Baushke wrote: > > >>> Content-Type: application/pgp; x-action=sign; format=text > > >> Well, where is such a content-type defined? > > > http://www.ipa.go.jp/security/rfc/RFC3156EN.html says: > > > Work on integrating PGP (Pretty Good Privacy) with MIME [3] > > (including the since withdrawn "application/pgp" content type) prior > > to RFC 2015 suffered from a number of problems, the most significant > > of which is the inability to recover signed message bodies without > > parsing data structures specific to PGP. > > ... > > [3] Freed, N. and N. Borenstein, "Multipurpose Internet Mail > > Extensions (MIME) Part Two: Media Types", RFC 2046, November > > 1996. > > > The problem is that the Mutt 'USING PGP FROM WITHIN MUTT' document > > > http://www.mutt.org/doc/PGP-Notes.txt > > > still specifies this withdrawn applications/pgp content-type and it > > appears to be a populate mechanism for mutt users to add pgp support. > > Ok. Gnus does anything particularly if they are used. And what > is better, making Gnus support it will give nobody trouble, I > think. So, I've modified mm-uu.el so as to recognize > applications/pgp message as text in the Gnus CVS repository. > I've also modified the default values for mm-inlined-types and > mm-uu-dissect-text-parts. > > The following is for Gnus 5.10.6, it requires that the patch I > sent in has been applied in advance. Okay, I backed out the mm-uu.el patch sent in . Then I applied the patch. Everything looks good with your patches. How should we note these fixes in our NEWS file when we release MH-E 7.90? Should we point folks at a union of the two patches to GNUS-5.10.6, or will there be an official gnus-5.10.7 sometime in the future for folks to use? While I have your attention about encrypted and signed e-mail messages... I will note that I have one private patch to gnus-5.10.6 that I reported to bugs@gnus.org on 2005-02-06 in <75396.1107736662@juniper.net> in which I wrote: | I am indirectly using the pgg-gpg-encrypt-region function when sending | gpg encrypted e-mail via the MH-E front-end under GNU Emacs 21.3. | | The e-mail is arriving with DOS line endings which is getting me some | complaints from my recipients who do not like ^M at the end of all of | their lines. | | The solution would seem to be to tell gpg that the messages are in | textmode via the --textmode option which allows the OpenPGP compatible | recipient program to insert whatever line-endings it wishes to consider | for 'text' mode. Of course, if someone is encrypting a binary | attachment, the use of '--textmode' would not be appropriate. | | When I patch my gnus 5.10.6 distribution as included below, the problem | goes away for text messages. This patch is NOT recommended for binary | data. | | I do not know how you will want to fix this problem in the real GNUS | distribution, but I think there should at least be some mechanism for a | function that is calling pgg-gpg-encrypt-region to specify that | --textmode should be passed to gpg. - --- gnus-5.10.6/lisp/pgg-gpg.el~ 2003-12-07 07:40:52.000000000 -0800 +++ gnus-5.10.6/lisp/pgg-gpg.el 2005-02-06 16:14:47.478961000 -0800 @@ -155,7 +155,7 @@ pgg-gpg-user-id))) (args (append - - (list "--batch" "--armor" "--always-trust" "--encrypt") + (list "--batch" "--textmode" "--armor" "--always-trust" "--encrypt") (if sign (list "--sign" "--local-user" pgg-gpg-user-id)) (if recipients (apply #'nconc I do not see any changes in how pgg-gpg-encrypt-region is handled in the CVS version of gnus. It would be nice to put this issue to bed. Thank you, -- Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFDzTTSCg7APGsDnFERAgA3AKDLw4Yar1YxQHBc4gJxwefJ+fBeswCgvJey L3kEBEuIgLeY0p6VM7GATVQ= =CX10 -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642