From: Kirk Strauser <kirk@strauser.com>
Subject: Re: I have to enter my passphrase twice?
Date: Mon, 05 May 2003 10:02:11 -0500 [thread overview]
Message-ID: <873cjt5te4.fsf@pooh.honeypot.net> (raw)
In-Reply-To: <878ytlpit9.fsf@pooh.honeypot.net> (Kirk Strauser's message of "Mon, 05 May 2003 09:30:26 -0500")
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
At 2003-05-05T14:30:26Z, Kirk Strauser <kirk@strauser.com> writes:
> As of recent, I have to enter my GnuPG passphrase twice when signing
> outgoing messages.
OK, I've narrowed down the trigger behavior slightly. It happens when I use
"<#secure method=pgp mode=sign>" to sign my email (instead of
"method=pgpmime"). When I hit C-c C-c to send my message, I get:
GnuPG passphrase for kirk@strauser.com:
After I enter it, I see:
Sending via mail...
flash briefly across the minibuffer. Then I get a second prompt:
GnuPG passphrase for kirk@strauser.com:
and only after I correctly re-enter my passphrase do I get the "Message
sent" message.
The supremely annoying part is that if I mis-enter my passphrase at the
second prompt, which I sometimes do because it's a fairly long phrase, then
the message gets sent twice.
Finally, I've set pgg-default-user-id to "8D02A6F1", which is the
fingerprint for my key. Why is it now sometimes prompting for the key for
"kirk@strauser.com", which is something it had never done before?
Did I manage to (require 'nsa-passphrase-logger) somewhere?
--
Kirk Strauser
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2003-05-05 15:02 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 [this message]
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
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=873cjt5te4.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).