From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/53961 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: Entering passphrase twice when sending PGP signed message Date: Sun, 14 Sep 2003 23:48:22 +0200 Sender: ding-owner@lists.math.uh.edu Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1063576118 15189 80.91.224.253 (14 Sep 2003 21:48:38 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 14 Sep 2003 21:48:38 +0000 (UTC) Cc: ding@gnus.org Original-X-From: ding-owner+M2501@lists.math.uh.edu Sun Sep 14 23:48:37 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19yejU-0001ga-00 for ; Sun, 14 Sep 2003 23:48:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19yejP-0004oE-00; Sun, 14 Sep 2003 16:48:31 -0500 Original-Received: from sclp3.sclp.com ([64.157.176.121]) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19yejL-0004o9-00 for ding@lists.math.uh.edu; Sun, 14 Sep 2003 16:48:27 -0500 Original-Received: (qmail 31139 invoked by alias); 14 Sep 2003 21:48:26 -0000 Original-Received: (qmail 31134 invoked from network); 14 Sep 2003 21:48:26 -0000 Original-Received: from 178.230.13.217.in-addr.dgcsystems.net (HELO yxa.extundo.com) (217.13.230.178) by sclp3.sclp.com with SMTP; 14 Sep 2003 21:48:26 -0000 Original-Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h8ELmMdk001592 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Sun, 14 Sep 2003 23:48:23 +0200 Original-To: Hrvoje Niksic Mail-Copies-To: nobody X-Payment: hashcash 1.2 0:030914:hniksic@xemacs.org:d21f596d85689581 X-Hashcash: 0:030914:hniksic@xemacs.org:d21f596d85689581 X-Payment: hashcash 1.2 0:030914:ding@gnus.org:6952d2d734d74913 X-Hashcash: 0:030914:ding@gnus.org:6952d2d734d74913 In-Reply-To: (Hrvoje Niksic's message of "Sun, 14 Sep 2003 19:17:41 +0200") User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:53961 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:53961 Hrvoje Niksic writes: > Simon Josefsson writes: > >> I agree, but to clarify, I think the passphrase cache should have a >> few modes: (I'm not sure the modes marked with '(?)' are useful.) >> >> * Disabled. >> * Enabled for decrypt. (?) >> * Enabled for sign. (?) >> * Enabled for decrypt and sign. >> * Enabled for decrypt and sign, but require confirmation for sign. >> * Enabled for decrypt and sign, but require confirmation for decrypt. (?) >> * Enabled for decrypt and sign, but require confirmation. >> >> I.e., I didn't mean PGG should ask for a passphrase and then issue >> yes-or-no-p, instead I meant that if the passphrase is cached, PGG >> should use yes-or-no-p before using the cache. > > I still believe that caching should be orthogonal to using > yes-or-no-p. That is, if confirmation is required for signing, I > should be required to confirm. Then, depending on whether passphrase > has been cached or not, I may or may not also have to type in the > passphrase. If you run with a disabled passphrase cache, I don't think this would result in a sensible user interface. Specifically: you would have to enter the passphrase AND type 'yes' every time. I would be rather annoyed by the useless yes-or-no-p query in this situation. Entering the passphrase is, to me at least, the same as approving the operation. > On the other hand, does it really happen to you that you could sign > something by mistake? When I was signing my mail, I had to press `C-c > C-m s o' [1] to add the appropriate MML markup -- it didn't happen > automagically. It happens for me automatically, I have some hooks that look up an attribute in my bbdb that say if I should add a MML encrypt tag, per recipient. But my customization is buggy (naturally), so sometimes it add a MML tag erroneously, and I rarely notice until I try to send the message. But since there is a passphrase prompt (or would be a yes-or-no-p) I can C-g and remove the MML tag. > Who ever came up with those key bindings?? Can you find a better, unallocated, key binding, that doesn't conflict with some mode that often can be enabled in message buffers?