Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: Daiki Ueno <ueno@unixuser.org>
Subject: Re: "epa (Caching Passphrases)"
Date: Wed, 06 Oct 2010 07:22:28 -0500	[thread overview]
Message-ID: <87y6abh5ob.fsf@lifelogs.com> (raw)
In-Reply-To: <m3mxqr3hz8.fsf_-_-ueno@unixuser.org>

On Wed, 06 Oct 2010 16:20:27 +0900 Daiki Ueno <ueno@unixuser.org> wrote: 

DU> Tassilo Horn <tassilo@member.fsf.org> writes:
>> The real problem was that I use GnuPG2, and with that, there's no way
>> to cache passwords on the lisp level.  But when you set up the
>> gpg-agent properly (exactly as the docs state), then that will do the
>> caching so that you are only asked once per file (in a certain time
>> frame).

DU> I added some notes on (current) password caching mechanisms provided by
DU> GnuPG2 and EasyPG Assistant, in (info "(epa) Caching Passphrases").

DU> I think it would be nice to link to it from (info "(auth) Help for
DU> users").  Since current doc is confusing nowadays:

DU>      ;;; VERY important if you want symmetric encryption
DU>      ;;; irrelevant if you don't
DU>      (setq epa-file-cache-passphrase-for-symmetric-encryption t)

Unfortunately Gnus is distributed alone as well, so a info link would
not work everywhere.  Can you suggest a rewrite of that section in
addition to the link to help people in that situation?

Thanks
Ted




  reply	other threads:[~2010-10-06 12:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27  0:09 auth-sources: 8 password prompts for accessing one single imap server Tassilo Horn
2010-09-27  6:38 ` Vegard Vesterheim
2010-09-27  7:59   ` Drew Hess
2011-02-25 22:19     ` Ted Zlatanov
2010-09-27 16:49   ` Lars Magne Ingebrigtsen
2010-09-27 17:13     ` Vegard Vesterheim
2010-09-27 17:21       ` Lars Magne Ingebrigtsen
2010-09-27 20:50         ` Tassilo Horn
2010-09-27 20:57           ` Lars Magne Ingebrigtsen
2010-09-30  6:30             ` Tassilo Horn
2010-09-30 15:44               ` Ted Zlatanov
2010-10-05  7:16                 ` Tassilo Horn
2010-10-06  7:20                   ` "epa (Caching Passphrases)" Daiki Ueno
2010-10-06 12:22                     ` Ted Zlatanov [this message]
2010-10-06 12:38                       ` Daiki Ueno
2010-10-06 12:52                         ` Ted Zlatanov
2010-10-06 13:25                           ` Daiki Ueno
2010-10-07 19:38                             ` Lars Magne Ingebrigtsen
2010-10-08 15:38                             ` Ted Zlatanov
2010-09-27 21:01           ` auth-sources: 8 password prompts for accessing one single imap server Ted Zlatanov
2010-09-27 21:42             ` Tassilo Horn
2010-09-28  7:25             ` Gijs Hillenius
2010-09-28 10:19               ` Lars Magne Ingebrigtsen
2010-09-28 10:32                 ` Gijs Hillenius
2010-09-28 12:04                   ` Dave Goldberg
2010-09-28 13:10                     ` Gijs Hillenius
2010-09-28 13:42                       ` Gijs Hillenius
2010-09-27 16:54 ` Lars Magne Ingebrigtsen
2010-09-27 18:37   ` Ted Zlatanov
2010-09-27 18:48     ` Lars Magne Ingebrigtsen
2010-09-27 18:52       ` Ted Zlatanov

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=87y6abh5ob.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=ueno@unixuser.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).