From: "Peter Münster" <pmlists@free.fr>
To: ding@gnus.org
Subject: Re: epg + pinentry + gnus
Date: Thu, 18 Sep 2014 20:44:28 +0200 [thread overview]
Message-ID: <87egv86a5v.fsf@micropit.roche-blanche.homenet.org> (raw)
In-Reply-To: <87oaudtvoa.fsf@sergiodj.net>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Thu, Sep 18 2014, Sergio Durigan Junior wrote:
> I use EasyPG (with gpg-agent) + Gnus, like many others, I believe.
> However, there's one thing that I can't do: make Gnus (or epg, for that
> matter) prompt me only once for the passphrase and then make gpg-agent
> cache it. What happens instead is that whenever I open an encrypted
> message, I see the passphrase prompt in the minibuffer.
Just some ideas:
- Keep passphrase in ram forever, put these lines in
~/.gnupg/gpg-agent.conf:
default-cache-ttl 99999999
max-cache-ttl 99999999
- Allow preset passphrase for secret keys, put this in
~/.gnupg/gpg-agent.conf:
allow-preset-passphrase
- Apply passphrase to all secret keys at start of session, put this in
~/.xinitrc:
SSH_ASKPASS=~/bin/askpass.lisp ssh-add
(file ~/bin/askpass.lisp is attached)
--
Peter
[-- Attachment #2: askpass.lisp --]
[-- Type: application/octet-stream, Size: 631 bytes --]
#!/usr/bin/sbcl --script
;; vielleicht so:
;; gpg --list-secret-keys --with-fingerprint --with-fingerprint --with-colon
;; --list-options no-show-unusable-uids,no-show-unusable-subkeys | sed -rn 's/^fpr:::::::::(.*):/\1/p'
(defvar *fingerprints*
(list "xxx"
"yyy"
"zzz"))
(with-output-to-string (out)
(run-program "/usr/lib/ssh/ssh-askpass" nil :output out)
(let ((s (get-output-stream-string out)))
(dolist (fp fingerprints)
(with-input-from-string (in s)
(run-program "/usr/lib64/gpg-preset-passphrase" (list "--preset" fp)
:input in :output nil)))
(princ s)))
next prev parent reply other threads:[~2014-09-18 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 4:11 Sergio Durigan Junior
2014-09-18 18:44 ` Peter Münster [this message]
2014-09-25 2:50 ` Sergio Durigan Junior
2014-10-03 6:31 ` W. Greenhouse
2014-09-24 15:09 ` Ted Zlatanov
2014-09-25 2:51 ` Sergio Durigan Junior
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=87egv86a5v.fsf@micropit.roche-blanche.homenet.org \
--to=pmlists@free.fr \
--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).