Re: PGG default values

[Jorge Godoy <godoy@ieee.org>]

Simon Josefsson <jas@extundo.com> 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. 

> 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...). 


See you,
-- 
Godoy.     <godoy@ieee.org>