From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/54764 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: PGG default values Date: Mon, 10 Nov 2003 17:19:11 +0100 Sender: ding-owner@lists.math.uh.edu Message-ID: References: <13408.1068408992@chicory.stanford.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1068481186 30429 80.91.224.253 (10 Nov 2003 16:19:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 10 Nov 2003 16:19:46 +0000 (UTC) Cc: "Satyaki Das" Original-X-From: ding-owner+M3305@lists.math.uh.edu Mon Nov 10 17:19:42 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 1AJElS-0006L9-00 for ; Mon, 10 Nov 2003 17:19:42 +0100 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 1AJElH-0001RN-00; Mon, 10 Nov 2003 10:19:31 -0600 Original-Received: from justine.libertine.org ([66.139.78.221]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1AJElC-0001RI-00 for ding@lists.math.uh.edu; Mon, 10 Nov 2003 10:19:27 -0600 Original-Received: from yxa.extundo.com (178.230.13.217.in-addr.dgcsystems.net [217.13.230.178]) by justine.libertine.org (Postfix) with ESMTP id 7044D3A004C for ; Mon, 10 Nov 2003 10:19:25 -0600 (CST) Original-Received: from latte (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.12.10/8.12.10) with ESMTP id hAAGJM1L012254 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 10 Nov 2003 17:19:23 +0100 Original-To: ding Mail-Copies-To: nobody X-Payment: hashcash 1.2 0:031110:ding@gnus.org:9b3ce8ea006550c5 X-Hashcash: 0:031110:ding@gnus.org:9b3ce8ea006550c5 X-Payment: hashcash 1.2 0:031110:satyakid@stanford.edu:33b9b0db541fa2c6 X-Hashcash: 0:031110:satyakid@stanford.edu:33b9b0db541fa2c6 In-Reply-To: (Jorge Godoy's message of "Mon, 10 Nov 2003 13:12:00 -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:54764 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:54764 Jorge Godoy writes: > Simon Josefsson writes: > >> I think the first one should default to t. Sending encrypted messages >> and later discovering you can't read them yourself would be a bad >> experience. People that understands enough to worry about a default >> setting of t will certainly be able to search for the variable in the >> manual and disable it. Opinions? > > I'd rather stick with that option in the ~/.gnupg/options file > only. There you can say if you want the message / document / whatever > to be encrypted for you or not. This is a better solution since it is > global for all programs that use GPG. Right, but do most users enable this? Is it enabled by default by GnuPG? If so, requesting encrypt-for-me again should be harmless, so wouldn't cause any problems. If not, people might send encrypted messages they can't read later on, which is bad. So I only see advantages with a default value of t, but no disadvantages. >> For the second one, I think 16 seconds is a rather pointless cache >> (maybe only to fix the extra invocation of gpg for GCC). But I >> don't know what a good default would be. An hour? A workday? >> Opinions? As you can infer from my settings, I lean towards >> infinity, but perhaps a more conservative setting should be used. > > I use 5 minutes. Usually I'm sending more than one encrypted message, > but I don't want the passphrase to be cached for too long. I used to > use one minute, but it bored me. > >> I suspect a good feature request at this point would be to add a >> yes-or-no-p on whether to use a cached passphrase, but until someone >> else mention I'll pretend I haven't thought about it. :-) If such a >> query is added, having an infinite passphrase cache might make >> sense. > > I don't think so. This somewhat violates the idea of knowing the > passphrase to use the encryption. From 3 to 5 minutes is what I think > ideal for a cache (and I think that this is a lot of time...). Thanks for your opinion. So now we have suggestions for ~5 minutes and ~10 minutes, if I recall correctly.