From: "Satyaki Das" <satyakid@stanford.edu>
Subject: Re: PGG default values (was: Re: PGG with multiple GnuPG keys)
Date: Sun, 09 Nov 2003 18:31:00 -0800 [thread overview]
Message-ID: <23580.1068431460@chicory.stanford.edu> (raw)
In-Reply-To: <ilufzgxnqxg.fsf_-_@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> Looking at my ~/.emacs I (only) have these two:
>
> '(pgg-encrypt-for-me t)
> '(pgg-passphrase-cache-expiry 12345678)
>
> The defaults are nil and 16 respectively.
>
> 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?
Yes it should default to t. I actually didn't know about the
option. But I already have some option in ~/.gnupg/options that
does the equivalent.
> 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?
Personally I have it set to 1000000. But the paranoid among us
will prefer a smaller value. I would say something of the order of
10 minutes shouldn't be too bad.
Satyaki
next prev parent reply other threads:[~2003-11-10 2:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-08 21:43 PGG with multiple GnuPG keys Satyaki Das
2003-11-09 4:04 ` Simon Josefsson
2003-11-09 20:16 ` Satyaki Das
2003-11-09 21:45 ` Simon Josefsson
2003-11-09 22:00 ` PGG default values (was: Re: PGG with multiple GnuPG keys) Simon Josefsson
2003-11-09 22:22 ` PGG default values Jesper Harder
2003-11-10 2:31 ` Satyaki Das [this message]
2003-11-10 3:13 ` Simon Josefsson
2003-11-10 15:12 ` Jorge Godoy
2003-11-10 16:19 ` Simon Josefsson
2003-11-10 20:53 ` Jorge Godoy
2003-11-10 2:20 ` PGG with multiple GnuPG keys Satyaki Das
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23580.1068431460@chicory.stanford.edu \
--to=satyakid@stanford.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).