From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daiki Ueno Newsgroups: gmane.emacs.devel Subject: Re: Documenting gpg-agent Date: Mon, 25 Dec 2006 07:45:07 +0900 Message-ID: <07267757-097d-4e9a-9189-d24d85b1786f@well-done.deisui.org> References: <2cd46e7f0612230904s7059393co2ed34a756775ee84@mail.gmail.com> NNTP-Posting-Host: dough.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1167000348 19124 80.91.229.10 (24 Dec 2006 22:45:48 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 24 Dec 2006 22:45:48 +0000 (UTC) Cc: wilde@sha-bang.de, Werner Koch , Ken Manheimer , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 24 23:45:46 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by dough.gmane.org with esmtp (Exim 4.50) id 1Gyc6D-0000oq-EV for ged-emacs-devel@m.gmane.org; Sun, 24 Dec 2006 23:45:45 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gyc6D-0004RS-1F for ged-emacs-devel@m.gmane.org; Sun, 24 Dec 2006 17:45:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gyc60-0004PQ-Nt for emacs-devel@gnu.org; Sun, 24 Dec 2006 17:45:32 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gyc5y-0004NB-5j for emacs-devel@gnu.org; Sun, 24 Dec 2006 17:45:32 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gyc5y-0004N2-17 for emacs-devel@gnu.org; Sun, 24 Dec 2006 17:45:30 -0500 Original-Received: from [210.231.96.69] (helo=localhost) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Gyc5w-0007Lx-DV; Sun, 24 Dec 2006 17:45:29 -0500 Original-Received: from localhost ([127.0.0.1] helo=well-done.deisui.org) by localhost with esmtp (Exim 4.63) (envelope-from ) id 1Gyc5b-0001OS-6h; Mon, 25 Dec 2006 07:45:07 +0900 Original-To: rms@gnu.org X-Attribution: DU Mail-Copies-To: poster In-Reply-To: (Richard Stallman's message of "Sat, 23 Dec 2006 20:35:56 -0500") User-Agent: T-gnus/6.17.2 (based on No Gnus v0.2) EMIKO/1.14.1 (Choanoflagellata) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 EasyPG/0.0.8 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (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:64224 Archived-At: >>>>> In >>>>> Richard Stallman wrote: > when the agent is active, passphrases passed in to > pgg are effectively ignored, such that pgg-agent continues to prompt > (via pinentry) for the passphrase. > That sounds like a bug in pgg or gpg-agent. Passing in passphrases > from the caller may not be recommended use, but it shouldn't just stop > working. Since allout exploits the use of PGG's passphrase handling functions to provide a custom passphrase handling, it's not a bug in PGG or gpg-agent, I think. Ken, is it hard to make allout skip its own passphrase handling if pgg-gpg-use-agent is t, as PGG does? I know it disables passphrase caching for symmetric encryption, but it seems a practical solution for the release. -- Daiki Ueno