From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: "Arne Jørgensen" <arne@arnested.dk>, ding@gnus.org
Subject: Re: password-cache-expiry and encrypt-password-cache-expiry
Date: 24 Feb 2005 12:47:50 -0500 [thread overview]
Message-ID: <4n650hn92x.fsf@lifelogs.com> (raw)
In-Reply-To: <iluzmxwmrtv.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 22 Feb 2005 18:23:40 +0100")
On Tue, 22 Feb 2005, jas@extundo.com wrote:
> Arne Jørgensen <arne@arnested.dk> writes:
>
>> Arne Jørgensen <arne@arnested.dk> writes:
>>
>>> (smime-ask-passphrase): Use `password-read-and-add' to read (and
>>> cache) password.
>>
>> I noticed that `encrypt-password-cache-expiry' defaults to 200 seconds
>> _and_ when set, sets `password-cache-expiry' (default value 16
>> seconds) too.
>>
>> Since both are loaded by gnus the value of `password-cache-expiry'
>> ends up being 200 seconds. Is this wise?
>
> I don't think so.
>
> I removed e-p-c-e, it wasn't used except as part of the custom group,
> and added the password-* variables to the defgroup MEMBERS parameter,
> so they will end up in the encrypt custom group as well.
This is fine. I meant to fix it, myself, but forgot about it. Sorry.
Thanks for catching it, Arne.
Ted
next prev parent reply other threads:[~2005-02-24 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 16:24 Patch for smime-stuff Arne Jørgensen
2005-02-22 16:54 ` Simon Josefsson
2005-02-22 17:07 ` password-cache-expiry and encrypt-password-cache-expiry (was: Patch for smime-stuff) Arne Jørgensen
2005-02-22 17:23 ` password-cache-expiry and encrypt-password-cache-expiry Simon Josefsson
2005-02-24 17:47 ` Ted Zlatanov [this message]
2005-02-22 22:21 ` Patch for smime-stuff Arne Jørgensen
2005-02-22 23:51 ` Simon Josefsson
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=4n650hn92x.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=arne@arnested.dk \
--cc=ding@gnus.org \
/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).