From: Daiki Ueno <ueno@unixuser.org>
Cc: wilde@sha-bang.de, Werner Koch <wk@gnupg.org>,
Ken Manheimer <ken.manheimer@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Documenting gpg-agent
Date: Mon, 25 Dec 2006 07:45:07 +0900 [thread overview]
Message-ID: <07267757-097d-4e9a-9189-d24d85b1786f@well-done.deisui.org> (raw)
In-Reply-To: <E1GyIHM-00035O-FV@fencepost.gnu.org> (Richard Stallman's message of "Sat, 23 Dec 2006 20:35:56 -0500")
>>>>> In <E1GyIHM-00035O-FV@fencepost.gnu.org>
>>>>> Richard Stallman <rms@gnu.org> wrote:
> when the agent is active, passphrases passed in to
> pgg are effectively ignored, such that pgg-agent continues to prompt
> (via pinentry) for the passphrase.
> That sounds like a bug in pgg or gpg-agent. Passing in passphrases
> from the caller may not be recommended use, but it shouldn't just stop
> working.
Since allout exploits the use of PGG's passphrase handling functions to
provide a custom passphrase handling, it's not a bug in PGG or gpg-agent,
I think.
Ken, is it hard to make allout skip its own passphrase handling if
pgg-gpg-use-agent is t, as PGG does? I know it disables passphrase
caching for symmetric encryption, but it seems a practical solution for
the release.
--
Daiki Ueno
next prev parent reply other threads:[~2006-12-24 22:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 14:59 Documenting gpg-agent Richard Stallman
2006-12-17 18:44 ` Sascha Wilde
2006-12-17 18:56 ` Sascha Wilde
2006-12-18 15:59 ` Richard Stallman
2006-12-23 17:04 ` Ken Manheimer
2006-12-23 17:25 ` David Kastrup
2006-12-23 18:11 ` Ken Manheimer
2006-12-24 1:35 ` Richard Stallman
2006-12-24 22:45 ` Daiki Ueno [this message]
2006-12-25 16:53 ` Richard Stallman
2006-12-26 1:01 ` Daiki Ueno
2006-12-28 14:21 ` Sascha Wilde
2007-02-15 16:33 ` Ken Manheimer
2007-02-17 20:57 ` Richard Stallman
2006-12-25 17:39 ` Ken Manheimer
2006-12-17 23:19 ` Chong Yidong
2006-12-18 15:59 ` Richard Stallman
2006-12-24 1:06 ` Chong Yidong
2006-12-24 17:09 ` Richard Stallman
2006-12-24 20:55 ` Chong Yidong
2006-12-25 17:37 ` Chong Yidong
2006-12-26 17:22 ` Richard Stallman
2006-12-31 13:08 ` Sascha Wilde
2006-12-31 22:13 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07267757-097d-4e9a-9189-d24d85b1786f@well-done.deisui.org \
--to=ueno@unixuser.org \
--cc=emacs-devel@gnu.org \
--cc=ken.manheimer@gmail.com \
--cc=wilde@sha-bang.de \
--cc=wk@gnupg.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).