From: "Bjørn Mork" <bmork@dod.no>
To: ding@gnus.org
Subject: Re: Caching passphrases
Date: Wed, 07 May 2008 15:02:48 +0200 [thread overview]
Message-ID: <87y76m2rnr.fsf@obelix.mork.no> (raw)
In-Reply-To: <m2r6cel1uc.fsf@nwalsh.com>
Norman Walsh <ndw@nwalsh.com> writes:
> I'm not sure if this is an EPG issue or a Gnus issue or soemthing else,
> but I encounter it in gnus so... :-)
>
> Everytime I send mail, I'm asked for my passphrase in order to sign the
> message. But I've noticed that if I have a couple of draft messages and
> I send them in rapid succession, I'm not asked for the second message.
>
> This suggests that *someone* is remembering my passphrase for a few
> seconds (or perhaps it suggests some deeper issue, I suppose).
>
> Anyway, I'd be perfectly content to trade a little security for a
> little convenience. Is there any way I can tell EPG/Gnus to remember
> my passphrase for some longer period of time?
This is controlled by mml2015-passphrase-cache-expiry, which defaults to
mml-secure-passphrase-cache-expiry, which defaults to
password-cache-expiry which defaults to 16
So, by default your passphrase is cached for 16 seconds as you've
noticed.
Bjørn
--
Only a lamer like you would say that the more bug fixes you have, the
better
prev parent reply other threads:[~2008-05-07 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 12:45 Norman Walsh
2008-05-07 13:02 ` Bjørn Mork [this message]
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=87y76m2rnr.fsf@obelix.mork.no \
--to=bmork@dod.no \
--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).