From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: ding@gnus.org
Subject: Re: epg + pinentry + gnus
Date: Wed, 24 Sep 2014 22:51:19 -0400 [thread overview]
Message-ID: <878ul8s994.fsf@sergiodj.net> (raw)
In-Reply-To: <87fvfhm4vt.fsf@lifelogs.com>
On Wednesday, September 24 2014, Ted Zlatanov wrote:
> On Thu, 18 Sep 2014 00:11:17 -0400 Sergio Durigan Junior <sergiodj@sergiodj.net> wrote:
>
> SDJ> But before I decide to go with the (defadvice) thing, I decided to ask
> SDJ> here: do you guys have this same problem, and if so, how do you
> SDJ> workaround it?
>
> You can try dropping to GnuPG 1.x and caching a symmetric encryption
> key.
Thanks for the advice, Ted, but dropping to GPG 1.x is not something I'd
like to do. Anyway, I chose to extend the TTL of the key, so that I
don't have to type the passphrase every now and then.
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2014-09-25 2:51 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
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 [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=878ul8s994.fsf@sergiodj.net \
--to=sergiodj@sergiodj.net \
--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).