From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Gnus/PGG password problem
Date: Sun, 21 Dec 2003 05:35:26 +0100 [thread overview]
Message-ID: <ilusmjedbzl.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87smjf5gvn.fsf@nwalsh.com> (Norman Walsh's message of "Sat, 20 Dec 2003 16:17:00 -0500")
Norman Walsh <ndw@nwalsh.com> writes:
> (require 'pgg)
>
> (setq pgg-cache-passphrase t)
These shouldn't be needed with CVS.
> With the setup above, using Gnus 5.10.2, when I send a signed message,
> it asks me for my key three times in a row (apparently once for each
> destination that the message goes to, the outside world, the current
> group, and the monthly archive group).
>
> What's more, if I send another message right away, it asks me three
> times again. It appears not to be caching the passphrase.
>
> Clues, please?
Perhaps this is solved in Gnus 5.10.3 (i.e., CVS)? I believe the
passphrase cache didn't work in 5.10.2.
next prev parent reply other threads:[~2003-12-21 4:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 21:17 Norman Walsh
2003-12-20 21:47 ` Ivan Boldyrev
2003-12-21 4:35 ` Simon Josefsson [this message]
2003-12-21 15:53 ` Norman Walsh
2003-12-21 16:09 ` Bijan Soleymani
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=ilusmjedbzl.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--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).