From: Norman Walsh <ndw@nwalsh.com>
Subject: Gnus/PGG password problem
Date: Sat, 20 Dec 2003 16:17:00 -0500 [thread overview]
Message-ID: <87smjf5gvn.fsf@nwalsh.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
I've been using mailcrypt for years, but someone recently pointed out
that MIME is now the "standard" way to do signing. Fair enough, I'd be
happy to make the messages look a little less awkward in
non-encryption aware readers anyway.
So I'm trying to switch to PGG. I've removed all the mailcrypt stuff from
my .gnus file and replaced it with:
;; PGG
(require 'pgg)
(setq pgg-cache-passphrase t)
(setq pgg-passphrase-cache-expiry 3600)
;; Emacs should always decrypt and verify emails automatically
(setq mm-verify-option 'always)
(setq mm-decrypt-option 'always)
;; Automcatically sign when sending mails
(defun will-you-sign ()
(interactive)
(if (y-or-n-p "Do you want to sign this message? ")
(mml-secure-message-sign-pgpmime)))
(add-hook 'gnus-message-setup-hook 'will-you-sign)
In a few minutes I'll probably get around to replacing will-you-sign with
sign-always, but that isn't the issue.
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?
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | The years teach us much which the days
http://nwalsh.com/ | never knew.-- Emerson
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2003-12-20 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 21:17 Norman Walsh [this message]
2003-12-20 21:47 ` Ivan Boldyrev
2003-12-21 4:35 ` Simon Josefsson
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=87smjf5gvn.fsf@nwalsh.com \
--to=ndw@nwalsh.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).