From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daiki Ueno Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: Small patch to enable use of gpg-agent with pgg Date: Wed, 22 Mar 2006 18:16:48 +0900 Message-ID: References: <2cd46e7f0510031250u66ea1349yb437d539ce4027ef@mail.gmail.com> <2cd46e7f0510061541w73bb6a92wb6d22829b6e804ae@mail.gmail.com> <20051007100014.GB4850@kenny.sha-bang.local> <2cd46e7f0510071106k3d4d3e6agc36f16a37d8b6bc6@mail.gmail.com> <20051007214952.GA30235@kenny.sha-bang.local> <20051008103627.GA1218@kenny.sha-bang.local> <2cd46e7f0510081131h14e2bbeaga7f1a33ebd6347c8@mail.gmail.com> <2cd46e7f0510101415t76825ea7u9749fe23da54ce@mail.gmail.com> <2cd46e7f0510121647x3c51fb65pc883ed61f4e864ab@mail.gmail.com> <2cd46e7f0510200708x4640d1c2t50743cf439e52dd4@mail.gmail.com> <87pskfq361.fsf@latte.josefsson.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1143019061 21440 80.91.229.2 (22 Mar 2006 09:17:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 22 Mar 2006 09:17:41 +0000 (UTC) Cc: emacs-devel@gnu.org, ding@gnus.org, Simon Josefsson Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 22 10:17:36 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FLzT7-00057v-IU for ged-emacs-devel@m.gmane.org; Wed, 22 Mar 2006 10:17:30 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FLzTK-0002n6-ME for ged-emacs-devel@m.gmane.org; Wed, 22 Mar 2006 04:17:42 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FLzT6-0002n1-7w for emacs-devel@gnu.org; Wed, 22 Mar 2006 04:17:28 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FLzSz-0002mL-7C for emacs-devel@gnu.org; Wed, 22 Mar 2006 04:17:27 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FLzSz-0002mE-3e for emacs-devel@gnu.org; Wed, 22 Mar 2006 04:17:21 -0500 Original-Received: from [210.231.96.69] (helo=well-done.deisui.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FLzT3-0006lz-TG for emacs-devel@gnu.org; Wed, 22 Mar 2006 04:17:26 -0500 Original-Received: from [150.82.173.221] (helo=well-done.deisui.org) by well-done.deisui.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1FLzSV-0004Tc-4y; Wed, 22 Mar 2006 18:16:51 +0900 Original-To: Sascha Wilde X-Attribution: DU In-Reply-To: (Sascha Wilde's message of "Wed, 22 Mar 2006 09:36:51 +0100") User-Agent: T-gnus/6.17.2 (based on No Gnus v0.2) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 17) (Jumbo Shrimp) (i686-pc-linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:51952 gmane.emacs.gnus.general:62353 Archived-At: Hello, >>>>> In >>>>> Sascha Wilde wrote: > This is very error prone. As I wrote before on emacs-devel: there are > certain situations in which using the agent will fail -- even if it is > available: for example: on an text console running the standard > pin-entry program (which uses curses) from within emacs won't work. > That's why I think this option should be explicitly enabled by the user. > Another problem is, that checking for $GPG_AGENT_INFO is not > sufficient, the environment variable will stay set, even is the agent > was killed. That looks a bit complicated for me. Is there a choice of utilizing --status-fd output? That is, query a user for his passphrase only when gpg requested (i.e. we see NEED_PASSPHRASE) Though I know that this solution involves some coding to make use of asynchronous process, I expect that it is not so hard to implement. Regards, -- Daiki Ueno