Re: [PATCH] emacs: sign/encrypt replies to signed/encrypted messages
authorJani Nikula <jani@nikula.org>
Mon, 14 Apr 2014 17:51:35 +0000 (20:51 +0300)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 18:01:35 +0000 (10:01 -0800)
8f/09b0c65dce5cd55c362c915c32474bc57b8351 [new file with mode: 0644]

diff --git a/8f/09b0c65dce5cd55c362c915c32474bc57b8351 b/8f/09b0c65dce5cd55c362c915c32474bc57b8351
new file mode 100644 (file)
index 0000000..486cd67
--- /dev/null
@@ -0,0 +1,144 @@
+Return-Path: <jani@nikula.org>\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 9AD9E431FBD\r
+       for <notmuch@notmuchmail.org>; Mon, 14 Apr 2014 10:51:43 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.699\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5\r
+       tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 373igepBmwIT for <notmuch@notmuchmail.org>;\r
+       Mon, 14 Apr 2014 10:51:37 -0700 (PDT)\r
+Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com\r
+       [209.85.220.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id DC9CA431FBC\r
+       for <notmuch@notmuchmail.org>; Mon, 14 Apr 2014 10:51:36 -0700 (PDT)\r
+Received: by mail-vc0-f178.google.com with SMTP id im17so7725830vcb.23\r
+       for <notmuch@notmuchmail.org>; Mon, 14 Apr 2014 10:51:35 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=1e100.net; s=20130820;\r
+       h=x-gm-message-state:mime-version:in-reply-to:references:date\r
+       :message-id:subject:from:to:cc:content-type;\r
+       bh=vW3WQ9YPYD+1T6IcJ0ADqVa5Sg7mQt7NZDQX7x/boDw=;\r
+       b=b39xzwrCv8iK2yx467vPMJojkv+26LFIy5oYqlvNHb3q7lJkvTUiTqIVBa3KYRYUj9\r
+       GbNQMbxo4tyyQdD8cehzhK8chOohpQh+Ay0PEwdtKR7A2RO671UI2viLX50/EmNw7gz9\r
+       0KjTUt02jrUvQi09gFHuZG2AJpS/ph9Hz5LbhFP/RMliIQCjX9ePbdB029G0r9CqrXdx\r
+       HI/ly7s3Z4JGjOMEyK5ywJ1ds9m8yNPr77dp1h36QXWFIlE6JFj4j5OKyZ/JwzC67LEU\r
+       QBZtEfsCFUOLurvnXz+URaGU2fHJuHJ60bnOipLLVTw7URYDDmKK8+aZEPJ7NA2nlKMo\r
+       a/jQ==\r
+X-Gm-Message-State:\r
+ ALoCoQm5mVdT6PTGFQP3Ibvq+I3UVmQn7d7jSiwHvfp1eYhsCawZdiHgfuyJrmsODY4rAzsqKPUo\r
+MIME-Version: 1.0\r
+X-Received: by 10.220.92.135 with SMTP id r7mr37624586vcm.11.1397497895097;\r
+       Mon, 14 Apr 2014 10:51:35 -0700 (PDT)\r
+Received: by 10.58.171.65 with HTTP; Mon, 14 Apr 2014 10:51:35 -0700 (PDT)\r
+Received: by 10.58.171.65 with HTTP; Mon, 14 Apr 2014 10:51:35 -0700 (PDT)\r
+In-Reply-To: <8738hf25pa.fsf@maritornes.cs.unb.ca>\r
+References: <87a9f1c8aq.fsf@servo.finestructure.net>\r
+       <1396689486-19232-1-git-send-email-jani@nikula.org>\r
+       <8738hf25pa.fsf@maritornes.cs.unb.ca>\r
+Date: Mon, 14 Apr 2014 20:51:35 +0300\r
+Message-ID:\r
+ <CAB+hUn9YeDY0u4+1=ru6VZVBJar4YfAK=nhORLhOO0EmyO2K_g@mail.gmail.com>\r
+Subject: Re: [PATCH] emacs: sign/encrypt replies to signed/encrypted messages\r
+From: Jani Nikula <jani@nikula.org>\r
+To: David Bremner <david@tethera.net>\r
+Content-Type: multipart/alternative; boundary=047d7b66f5fb9caa6104f7045533\r
+Cc: Notmuch Mail <notmuch@notmuchmail.org>\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: Mon, 14 Apr 2014 17:51:43 -0000\r
+\r
+--047d7b66f5fb9caa6104f7045533\r
+Content-Type: text/plain; charset=UTF-8\r
+\r
+On Apr 14, 2014 10:17 AM, "David Bremner" <david@tethera.net> wrote:\r
+>\r
+> Jani Nikula <jani@nikula.org> writes:\r
+> > +(defun notmuch-mua-reply-crypto (parts)\r
+> > +  (loop for part in parts\r
+> > +     if (notmuch-match-content-type (plist-get part :content-type)\r
+"multipart/signed")\r
+> > +       do (mml-secure-message-sign)\r
+>\r
+> How do people feel about disabling/removing the previous two lines?\r
+>\r
+\r
+I'd be fine with that (see the commit message).\r
+\r
+Jani.\r
+\r
+> It's less obvious to me that you always want to sign in reply to a\r
+> signed message (probably you want to unconditionally always sign in that\r
+> case).  As written this causes some inconvenience  for users that have\r
+> notmuch-crypto-process-mime=t to verify inbound signatures, but don't\r
+> necessarily have the ability to sign outbound mail.\r
+>\r
+>\r
+> > +     else if (notmuch-match-content-type (plist-get part\r
+:content-type) "multipart/encrypted")\r
+> > +       do (mml-secure-message-sign-encrypt)\r
+> > +     else if (notmuch-match-content-type (plist-get part\r
+:content-type) "multipart/*")\r
+> > +       do (notmuch-mua-reply-crypto (plist-get part :content))))\r
+> > +\r
+\r
+--047d7b66f5fb9caa6104f7045533\r
+Content-Type: text/html; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+<p dir=3D"ltr"><br>\r
+On Apr 14, 2014 10:17 AM, &quot;David Bremner&quot; &lt;<a href=3D"mailto:d=\r
+avid@tethera.net">david@tethera.net</a>&gt; wrote:<br>\r
+&gt;<br>\r
+&gt; Jani Nikula &lt;<a href=3D"mailto:jani@nikula.org">jani@nikula.org</a>=\r
+&gt; writes:<br>\r
+&gt; &gt; +(defun notmuch-mua-reply-crypto (parts)<br>\r
+&gt; &gt; + =C2=A0(loop for part in parts<br>\r
+&gt; &gt; + =C2=A0 =C2=A0 if (notmuch-match-content-type (plist-get part :c=\r
+ontent-type) &quot;multipart/signed&quot;)<br>\r
+&gt; &gt; + =C2=A0 =C2=A0 =C2=A0 do (mml-secure-message-sign)<br>\r
+&gt;<br>\r
+&gt; How do people feel about disabling/removing the previous two lines?<br=\r
+>\r
+&gt;</p>\r
+<p dir=3D"ltr">I&#39;d be fine with that (see the commit message).</p>\r
+<p dir=3D"ltr">Jani.<br></p>\r
+<p dir=3D"ltr">&gt; It&#39;s less obvious to me that you always want to sig=\r
+n in reply to a<br>\r
+&gt; signed message (probably you want to unconditionally always sign in th=\r
+at<br>\r
+&gt; case). =C2=A0As written this causes some inconvenience =C2=A0for users=\r
+ that have<br>\r
+&gt; notmuch-crypto-process-mime=3Dt to verify inbound signatures, but don&=\r
+#39;t<br>\r
+&gt; necessarily have the ability to sign outbound mail.<br>\r
+&gt;<br>\r
+&gt;<br>\r
+&gt; &gt; + =C2=A0 =C2=A0 else if (notmuch-match-content-type (plist-get pa=\r
+rt :content-type) &quot;multipart/encrypted&quot;)<br>\r
+&gt; &gt; + =C2=A0 =C2=A0 =C2=A0 do (mml-secure-message-sign-encrypt)<br>\r
+&gt; &gt; + =C2=A0 =C2=A0 else if (notmuch-match-content-type (plist-get pa=\r
+rt :content-type) &quot;multipart/*&quot;)<br>\r
+&gt; &gt; + =C2=A0 =C2=A0 =C2=A0 do (notmuch-mua-reply-crypto (plist-get pa=\r
+rt :content))))<br>\r
+&gt; &gt; +<br>\r
+</p>\r
+\r
+--047d7b66f5fb9caa6104f7045533--\r