From: Kirk Strauser <kirk@strauser.com>
Subject: Re: I have to enter my passphrase twice?
Date: Mon, 05 May 2003 16:25:58 -0500 [thread overview]
Message-ID: <87n0i1krvd.fsf@pooh.honeypot.net> (raw)
In-Reply-To: <microsoft-free.87ade1xsay.fsf@eicq.dnsalias.org> (Steve Youngs's message of "Tue, 06 May 2003 02:38:13 +1000")
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
At 2003-05-05T16:38:13Z, Steve Youngs <youngs@xemacs.org> writes:
> I've seen this too, bloody annoying. You're using PGG, right? You
> can easily get around this by setting a passphrase cache:
You'd think. But I've set pgg-cache-passphrase to 't' and
pgg-passphrase-cache-expiry to '7200' and it didn't help. :-/
--
Kirk Strauser
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2003-05-05 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 14:30 Kirk Strauser
2003-05-05 14:56 ` Simon Josefsson
2003-05-05 15:02 ` Kirk Strauser
2003-05-05 15:55 ` Simon Josefsson
2003-05-05 16:22 ` Kirk Strauser
2003-05-05 17:22 ` Simon Josefsson
2003-05-05 19:11 ` Kirk Strauser
2003-05-05 19:32 ` Simon Josefsson
2003-05-05 16:38 ` Steve Youngs
2003-05-05 21:25 ` Kirk Strauser [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=87n0i1krvd.fsf@pooh.honeypot.net \
--to=kirk@strauser.com \
/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).