unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ken Manheimer" <ken.manheimer@gmail.com>
Cc: Sascha Wilde <wilde@sha-bang.de>, emacs-devel@gnu.org
Subject: Re: Documenting gpg-agent
Date: Sat, 23 Dec 2006 12:04:02 -0500	[thread overview]
Message-ID: <2cd46e7f0612230904s7059393co2ed34a756775ee84@mail.gmail.com> (raw)
In-Reply-To: <E1GwKu6-00014u-80@fencepost.gnu.org>

On 12/18/06, Richard Stallman <rms@gnu.org> wrote:

>     Since GnuPG2 and therefor gpg-agent is released, and we are
>     recommending its use: should we change the default value of
>     pgg-gpg-use-agent to t?
>
>     When no agent is available the old passphrase input/caching will still
>     be used as a fallback so changing the default should not do much harm.
>
> That seems like the right thing, but I don't really know anything
> about this, so I can't be sure.  Please let's wait a few days to see
> if anyone presents a valid objection.

my allout encryption provisions are badly disrupted with the new pgg
revision, when gpg-agent is active.  it may be that i can work around
that by inhibiting use of gpg-agent in my code (assuming that the new
pgg revisions provide an easy way to do that?).  the timing is bad,
though - i have one week before i'm away for three weeks, and my time
available for unexpected problems like this, up to then, is extremely
limited.  so i'm in a bind, and worried about it.

one problem shows with allout symmetric-key encryption.  allout
prompts for the passphrase, and then pinentry prompts (multiple times,
because allout is checking validity of the symmetric key against a
dummy string, as well as using it for the target text) on each
encryption and decryption.  allout's key caching works, so it doesn't
prompt the user until the cached entry times out, but pinentry still
prompts multiple times on every encryption and decryption.

i wonder whether the new pgg provisions are ignoring a passed-in
passphrase when one is provided?  that would render useless allout's
caching, as appears to be happening.

i'll look at having allout do transient inhibition of the new
gpg-agent provisions (eg, let-binding pgg-gpg-use-agent to nil), but
doubt i'll have time to look at the new pgg code to see about whether
passed-in passphrases are disregarded.  so barring the former
workaround, i doubt i'll have time to look at proper integration with
the new pgg provisions before late january.

--
ken
http://myriadicity.net

  reply	other threads:[~2006-12-23 17:04 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 [this message]
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
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=2cd46e7f0612230904s7059393co2ed34a756775ee84@mail.gmail.com \
    --to=ken.manheimer@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=wilde@sha-bang.de \
    /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).