Gnus development mailing list
 help / color / mirror / Atom feed
From: Gijs Hillenius <gijs@hillenius.net>
To: ding@gnus.org
Subject: Re: [gnus git] Add ~/.authinfo to the default, since that's probably most useful for users.
Date: Sat, 25 Sep 2010 14:47:23 +0200	[thread overview]
Message-ID: <87pqw2kn1g.fsf@hillenius.net> (raw)
In-Reply-To: <87fwx4h2xt.fsf@lifelogs.com>

On 20 Sep 2010, Ted Zlatanov wrote:


[...]

>>> auth-source.el has nothing to do with it.  All the work is done by
>>> EPA/EPG and I'm intentionally keeping auth-source.el agnostic of
>>> encryption issues beyond mentioning the .gpg extension.

[...]

> LMI> Will auth-source.el store the passwords that are queried anywhere?
> LMI> Like in the ~/.authinfo.gpg file?
>
> It caches them but doesn't save them.

Hello

I wonder about this caching. I've been reading the manual, and wonder if
I understand it correctly. I think I'm following 'the simple' example in
the docs.

my .authinfo.gpg contains two lines
machine 1 (mail)
machine 2 (usenet)

And Gnus accesses three machines, news, mail and gmane (among others for
reading this Ding here).

Now, Gnus at start-up currently asks me *six* times to decrypt
~/.authinfo.gpg and twice more when I send an email / news. I have cache
enabled, so I expected to be prompted just once, per Emacs session. Or
something.

in .emacs
,----
|  (require 'epa-file) (epa-file-enable)
| (setq epa-file-cache-passphrase-for-symmetric-encryption t)
`----

in .gnus

,----
| (setq auth-sources '((:source "~/.authinfo.gpg")))
`----






-- 
Anyone who goes to a psychiatrist ought to have his head examined.
		-- Samuel Goldwyn




  reply	other threads:[~2010-09-25 12:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1OwjUu-0007Om-00@quimby.gnus.org>
2010-09-18  6:19 ` Ted Zlatanov
2010-09-18 11:47   ` Lars Magne Ingebrigtsen
2010-09-20  2:30     ` Ted Zlatanov
2010-09-20  8:14       ` Lars Magne Ingebrigtsen
2010-09-20 15:03         ` Ted Zlatanov
2010-09-25 12:47           ` Gijs Hillenius [this message]
2010-09-25 13:56             ` Lars Magne Ingebrigtsen
2010-09-25 15:12             ` Ted Zlatanov
     [not found]               ` <87mxr46gv9.fsf@hillenius.net>
2010-09-26 12:27                 ` Ted Zlatanov
2010-09-26 12:38                   ` tls.el I added '--insecure' (Was :Re: [gnus git] Add ~/.authinfo to the default, since that's probably most useful for users.) Gijs Hillenius
2010-09-26 20:53                     ` tls.el I added '--insecure' Ted Zlatanov
2010-09-20 10:47       ` [gnus git] Add ~/.authinfo to the default, since that's probably most useful for users Sebastian Krause
2010-09-20 14:59         ` Ted Zlatanov
2010-09-20 18:40           ` Michael Albinus
2010-09-20 14:27       ` Richard Riley
2010-09-20 15:01         ` Ted Zlatanov
2010-09-20 15:29           ` Richard Riley
2010-09-18 12:50   ` Sebastian Krause
2010-09-18 15:40     ` Lars Magne Ingebrigtsen
2010-09-18 21:29       ` Sebastian Krause
2010-09-18 21:31         ` Lars Magne Ingebrigtsen
2010-09-20 11:03   ` Robert Pluim
2010-09-20 14:10     ` Richard Riley
2010-09-20 14:59       ` Robert Pluim
2010-09-20 15:26     ` Ted Zlatanov
2010-09-20 15:43       ` Tibor Simko
2010-09-20 15:53       ` Robert Pluim
2010-09-21 16:19       ` Lars Magne Ingebrigtsen

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=87pqw2kn1g.fsf@hillenius.net \
    --to=gijs@hillenius.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).