--- /dev/null
+Return-Path: <jrollins@finestructure.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id BFAF0431FB6\r
+ for <notmuch@notmuchmail.org>; Sat, 17 Jan 2015 14:55:03 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.138\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.138 tagged_above=-999 required=5\r
+ tests=[DNS_FROM_AHBL_RHSBL=2.438, RCVD_IN_DNSWL_MED=-2.3]\r
+ autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id QK1BsjEm9z01 for <notmuch@notmuchmail.org>;\r
+ Sat, 17 Jan 2015 14:55:00 -0800 (PST)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+ [131.215.239.19])\r
+ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 8ED34431FAF\r
+ for <notmuch@notmuchmail.org>; Sat, 17 Jan 2015 14:55:00 -0800 (PST)\r
+Received: from smtp02.caltech.edu (localhost [127.0.0.1])\r
+ by filter-return (Postfix) with ESMTP id A381E6C0469;\r
+ Sat, 17 Jan 2015 14:54:58 -0800 (PST)\r
+X-Spam-Scanned: at Caltech-IMSS on smtp02.caltech.edu by amavisd-new\r
+Received: from finestructure.net (cpe-104-173-172-86.socal.res.rr.com\r
+ [104.173.172.86])\r
+ (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))\r
+ (No client certificate requested) (Authenticated sender: jrollins)\r
+ by smtp-server.its.caltech.edu (Postfix) with ESMTPSA id 250476C0391;\r
+ Sat, 17 Jan 2015 14:54:58 -0800 (PST)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+ id E211D60142; Sat, 17 Jan 2015 14:54:57 -0800 (PST)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: David Bremner <david@tethera.net>, Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: Re: [PATCH] test: initial tests for smime\r
+In-Reply-To: <87sif99h3c.fsf@maritornes.cs.unb.ca>\r
+References: <87wq4ltbma.fsf@servo.finestructure.net>\r
+ <1421530691-14060-1-git-send-email-david@tethera.net>\r
+ <87twzpt6e8.fsf@servo.finestructure.net>\r
+ <87sif99h3c.fsf@maritornes.cs.unb.ca>\r
+User-Agent: Notmuch/0.19+28~g3915564 (http://notmuchmail.org) Emacs/24.4.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 17 Jan 2015 14:54:54 -0800\r
+Message-ID: <87r3utt3up.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+ micalg=pgp-sha256; protocol="application/pgp-signature"\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 17 Jan 2015 22:55:03 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+\r
+On Sat, Jan 17 2015, David Bremner <david@tethera.net> wrote:\r
+>> But do we really need to test the message output of openssl? It seems\r
+>> like it's broken, and if it ever gets fixed we'll need to change this\r
+>> test.\r
+>\r
+> I think it's not so much broken as "canonical". There is some discussion\r
+> in the openssl-smime man page that pointed me to RFC5751\r
+> para 3.1.1\r
+>\r
+> MIME entities of major type "text" MUST have both their line endings\r
+> and character set canonicalized. The line ending MUST be the pair of\r
+> characters <CR><LF>\r
+\r
+Interesting, and oh well. Not going to fall down that rabbit hole!\r
+\r
+>> But all we really care about is that openssl is properly verifying the\r
+>> message, yes? Why not just test that and forget about the rest of\r
+>> openssl's output?\r
+>\r
+> Maybe it doesn't add too much as long as the message is using the "clear\r
+> signed" multipart/signed format. On the other hand there is an opaque\r
+> signed format (application/pkcs7-mime with Signeddata) too, where it\r
+> would be interesting to check for mangling of the text. Similarly, when\r
+> we add a similar test for encryption, I think we do want to check the\r
+> content, so we'll have to figure this out at some point.\r
+\r
+But at any point are we using the output of the message piped through\r
+openssl? Does gmime (possibly via gpgsm) actually pipe the message\r
+through openssl before further parsing it? If so, then I guess we do\r
+care about what openssl does to the original message. If not, then I'm\r
+still not sure we care.\r
+\r
+jamie.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature; name="signature.asc"\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1\r
+\r
+iQIcBAEBCAAGBQJUuug+AAoJEO00zqvie6q8ZYsQAJe8WdWAjVbqWIBM//b0FXL7\r
+t2i9Jc658NyukDVjOyk0tC3ZL/nktupl1dg8Awn5ddTPNxjB8XVgAur1uXXZqwIS\r
+i6rJyQEPoLp/FyHKwr0ox+6Wtvoq6fl4nMy15nUexsGo1hFYgCnop9rWu786aRd+\r
+GOfMhEqk6NjxOygCMsYu+uBlnX0iusQ6BlkTnBf0h/2ULbajebNtNWtw4lfRspl3\r
+GkU9vTQvyQEXzcZZnxYswBWxtx3JZbni0dZvDhJWQm0bLY7pqyWPH+2e8iS/RDdL\r
+BbvIUVmaIHIHoFUkPQdWH/Nq1U0yHwjxEYsTpmJxmQav5+vu7SLa2RNOIDx7ovbx\r
+HRW1t0TUgNtN1Yy3bqq0T8lmraln7a1+Egwn9O+Ki9dNXidonInJwNyupBLwkaJc\r
+EGdl0ve3RsVPccfA4WLaxfG5S6odRgMdfB/HXmhAsDsAhO6vcjgJ5VsEBYES39f6\r
+OJRqc0g8j59iUk6FxJRs6b5nz/KmGUf5r0FV7xA7AmOh45o8w7sP07kq1LTbPHB6\r
+f5qassQc5LPjBgqmAhtc9ntWsmzFVE/E04WLGCId03AcStLp3GrqrICnfTXd3wXC\r
+3pU4hwXdW5ig9SEQaPqEkfsVLIuLLEP4qpcYfQKC7iotv1QE4Q2VIueYv5jWw41s\r
+1Rk/FI5SvJDnWaBQSG0g\r
+=/AJB\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r
projects / notmuch-archives.git / commitdiff