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: [bug] PGG shows ?? when prompt for passphrase Date: Sun, 17 Dec 2006 12:28:01 +0900 Message-ID: <93fed91b-cb8a-4de7-9a16-62c85654bab6@well-done.deisui.org> References: <8f26a84d-356a-44f1-ac6a-54792380b76d@well-done.deisui.org> NNTP-Posting-Host: dough.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1166326109 14205 80.91.229.10 (17 Dec 2006 03:28:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 17 Dec 2006 03:28:29 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 17 04:28:26 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 1GvmhM-00035X-JI for ged-emacs-devel@m.gmane.org; Sun, 17 Dec 2006 04:28:24 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GvmhL-00058d-VD for ged-emacs-devel@m.gmane.org; Sat, 16 Dec 2006 22:28:24 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gvmh8-000565-M2 for emacs-devel@gnu.org; Sat, 16 Dec 2006 22:28:10 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gvmh6-00052W-R5 for emacs-devel@gnu.org; Sat, 16 Dec 2006 22:28:10 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gvmh6-00052K-Mc for emacs-devel@gnu.org; Sat, 16 Dec 2006 22:28:08 -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 1Gvmh6-0000YT-53 for emacs-devel@gnu.org; Sat, 16 Dec 2006 22:28:08 -0500 Original-Received: from localhost ([127.0.0.1] helo=well-done.deisui.org) by localhost with esmtp (Exim 4.63) (envelope-from ) id 1Gvmgz-0007EF-Sd; Sun, 17 Dec 2006 12:28:01 +0900 Original-To: Leo X-Attribution: DU In-Reply-To: (Leo's message of "Sun, 17 Dec 2006 02:18:19 +0000") 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:63866 Archived-At: >>>>> In >>>>> Leo wrote: > In case of multiple private keys, then I won't be able to tell which > passphrase to input. So I still think this might be a bug. I agree with you that might be a bug. However, I think we can't make it perfect. For example see the comment on the above, ;; XXX the user is stuck if they need to use the passphrase for ;; any but the first secret key for which the message is ;; encrypted. ideally, we would incrementally give them a ;; chance with subsequent keys each time they fail with one. > I debug `pgg-gpg-decrypt-region' and found out the message-keys > returned by (pgg-decode-armor-region (point-min) (point-max)) is > something like "CF3FFFEF3FFF9B60A3FFF896D343FF8F" which has no way to > match the secret-keys because all of them are 8-char long. > I hope this is useful and thank you for looking into this. I'm afraid I won't do it because of two reasons. First, I think selecting a secret key for a PGP message is out of scope of PGG. It is a task of GnuPG. Second, nowadays gpg-agent is the recommended way to input passphrases. In that case, we don't need such a more-than-necessarily-complicated stuff at all. Regards, -- Daiki Ueno