From: Richard Riley <rileyrgdev@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Gnus and pgp
Date: Wed, 02 Dec 2009 20:08:11 +0100 [thread overview]
Message-ID: <hf6dv0$hbr$1@ger.gmane.org> (raw)
In-Reply-To: <87iqcqmoat.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Sun, 29 Nov 2009 19:35:17 +0100 Richard Riley <rileyrgdev@gmail.com> wrote:
>
> RR> I just wonder how many of you were using pgp and something like
> RR> gupg-agent?
>
> RR> I was having terrible connection problems for ages with a set up like
> RR> this:
>
> RR> ,----
> RR> | (require 'auth-source)
> RR> | (require 'epa-file)
> RR> | (setq epa-file-cache-passphrase-for-symmetric-encryption t) ;;VERY Important
> RR> | (if (file-exists-p "~/.authinfo")
> RR> | (setq auth-sources '((:source "~/.authinfo" :host t :protocol t)))
> RR> | (setq auth-sources '((:source "~/.authinfo.gpg" :host t :protocol t))))
> RR> | (setq
> RR> | mml2015-encrypt-to-self t
> RR> | mml2015-cache-passphrase t
> RR> | mml2015-passphrase-cache-expiry 60000
> RR> | mml2015-verbose t)
> RR> `----
>
> RR> When using the .gpg, hard to pinpoint but constant refusals to connect
> RR> to a server (nntp) when doing a refresh or even starting Gnus for the first
> RR> time. Often quitting gnus and then restarting fixed it. I know the
> RR> default above is .authinfo as that is my set up now (I just recreated
> RR> the .authinfo from the .gpg file) and all connection issues vanished.
>
> RR> Is anyone else here using the epa stuff with more success? Can you share
> RR> your setup? I would love to use the (chmodded) .authinfo and replace
> RR> with a .gpg but it doesn't seem very stable with my set up above.
>
> RR> I know the agent was running fine.
>
> I don't use the GnuPG agent, I just cache the passphrase locally. It
> works perfectly for me with heavy daily usage. Can you try that (set
> GPG_AGENT_INFO=none) and see if it works for you?
>
> Ted
I wasn't aware you could do that! Works reliably now indicating an issue
with emacs talking to the agent.
next prev parent reply other threads:[~2009-12-02 19:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11779.1259519753.2239.info-gnus-english@gnu.org>
2009-12-01 20:28 ` Ted Zlatanov
2009-12-02 19:08 ` Richard Riley [this message]
2009-12-02 19:20 ` Richard Riley
[not found] ` <mailman.12043.1259780939.2239.info-gnus-english@gnu.org>
2009-12-02 21:41 ` Ted Zlatanov
2009-12-03 0:54 ` Richard Riley
[not found] ` <mailman.12065.1259801678.2239.info-gnus-english@gnu.org>
2009-12-03 18:02 ` Ted Zlatanov
2009-12-03 19:11 ` Richard Riley
2009-12-07 18:54 ` Richard Riley
2009-12-22 18:08 ` Richard Riley
[not found] ` <mailman.2.1261505407.18930.info-gnus-english@gnu.org>
2010-01-05 19:28 ` Ted Zlatanov
2010-01-06 0:42 ` Richard Riley
[not found] ` <mailman.814.1263114758.18930.info-gnus-english@gnu.org>
2010-01-13 21:41 ` Ted Zlatanov
2010-01-14 0:19 ` Richard Riley
[not found] ` <mailman.1372.1263428412.18930.info-gnus-english@gnu.org>
2010-01-14 14:22 ` Ted Zlatanov
2010-01-14 15:36 ` Richard Riley
[not found] ` <mailman.1413.1263483604.18930.info-gnus-english@gnu.org>
2010-01-15 18:37 ` Ted Zlatanov
2009-11-29 18:35 Richard Riley
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='hf6dv0$hbr$1@ger.gmane.org' \
--to=rileyrgdev@gmail.com \
--cc=info-gnus-english@gnu.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).