Re: [PATCH 0/2] Prompting for the GPG password within Emacs

diff --git a/2d/0dc757e2ff23c2b3b2f18726d3c8521d9d448a b/2d/0dc757e2ff23c2b3b2f18726d3c8521d9d448a
new file mode 100644 (file)
index 0000000..f7949eb
--- /dev/null
+++ b/2d/0dc757e2ff23c2b3b2f18726d3c8521d9d448a
@@ -0,0 +1,91 @@
+Return-Path: <craven@gmx.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 74863431FAF\r
+       for <notmuch@notmuchmail.org>; Sun,  7 Jul 2013 23:45:50 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.001\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.001 tagged_above=-999 required=5\r
+       tests=[FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001]\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 STg2LSXJc5og for <notmuch@notmuchmail.org>;\r
+       Sun,  7 Jul 2013 23:45:43 -0700 (PDT)\r
+Received: from mout.gmx.net (mout.gmx.net [212.227.15.19])\r
+       by olra.theworths.org (Postfix) with ESMTP id B5A80431FAE\r
+       for <notmuch@notmuchmail.org>; Sun,  7 Jul 2013 23:45:42 -0700 (PDT)\r
+Received: from mail.nexoid.at ([178.79.130.240]) by mail.gmx.com (mrgmx101)\r
+       with ESMTPSA (Nemesis) id 0Lxt3Q-1UAqJB19SG-015MV1;\r
+       Mon, 08 Jul 2013 08:45:37 +0200\r
+Received: from nexoid (localhost [127.0.0.1])\r
+       by mail.nexoid.at (Postfix) with ESMTP id 8A3BEE01D;\r
+       Mon,  8 Jul 2013 08:45:36 +0200 (CEST)\r
+From: <craven@gmx.net>\r
+To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,\r
+       Neil Roberts <neil@linux.intel.com>\r
+Subject: Re: [PATCH 0/2] Prompting for the GPG password within Emacs\r
+In-Reply-To: <51D9F4E6.1030504@fifthhorseman.net>\r
+References: <1373195672-9338-1-git-send-email-neil@linux.intel.com>\r
+       <51D9F4E6.1030504@fifthhorseman.net>\r
+User-Agent: Notmuch/0.15.2+182~gd0bd88f (http://notmuchmail.org)\r
+       Emacs/24.3.50.1 (i686-pc-linux-gnu)\r
+Date: Mon, 08 Jul 2013 08:45:36 +0200\r
+Message-ID: <87wqp135yn.fsf@nexoid.at>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-Provags-ID: V03:K0:IVhD9GfVeOu35ZQSUzLvA+07yWQXir0E5WvR3Ma5BRagVCSKEG/\r
+       X6Aa44gjyAzlq7rE6GVhvG1ErxsnI5M0Oo+qut7Heniad7FsxmbDBbxqLqsg3HEVUNQ7HAD\r
+       FG511EG+SdJlCSJVOQ13TEtsksPfBBeTeUp7DXvkRzyLP9oqxPqBtm5ej0lyma/y8V7YD1w\r
+       y4QFp8U9Sv33AM/FFeODA==\r
+Cc: 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, 08 Jul 2013 06:45:50 -0000\r
+\r
+>> I've recently started using notmuch to try and read PGP-encrypted\r
+>> email. However the trouble is I normally access my email remotely via\r
+>> SSH and it's very difficult to get gpg-agent to work in those\r
+>> circumstances. I've therefore made some patches to try and get Emacs\r
+>> to prompt for the password. They are based on the way mml communicates\r
+>> with gpg by having two pipes so that notmuch can notify Emacs that it\r
+>> needs a password and it will reply on the other.\r
+\r
+This is what I have tried too :) My setup is as follows:\r
+I run emacs in non-window mode (-nw) on a server machine under tmux (a\r
+terminal multiplexer, like screen). I connect to this via SSH from\r
+different machines (maybe even across multiple SSH logins).\r
+\r
+> I strongly encourage you to get the gpg-agent model sorted out for your\r
+> use case, instead of moving in the direction of this patch series.\r
+> Can you describe what you've tried in terms of using gpg-agent?  where\r
+> are your secret keys stored?  are they on your local machine, or on the\r
+> remote machine?\r
+\r
+I have the secret keys on the local machine and the remote machine.\r
+gpg-agent runs fine on the remote machine, however I have found no way\r
+to make it consistently prompt for the password on the right SSH\r
+connection (I don't believe there even is a way to achieve this, as\r
+there may be multiple, or I may leave several connections open and move\r
+between machines). The only thing that mostly works is using the remote\r
+gpg-agent to prompt on the terminal, which messes up the display\r
+temporarily.\r
+\r
+I'd be really happy about any ideas how to solve this :)\r
+\r
+Greetings,\r
+\r
+Peter\r