From: "Ken Manheimer" <ken.manheimer@gmail.com>
Cc: Sascha Wilde <wilde@sha-bang.de>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Documenting gpg-agent
Date: Sat, 23 Dec 2006 13:11:17 -0500 [thread overview]
Message-ID: <2cd46e7f0612231011k10b09b85y140ff04347bd4632@mail.gmail.com> (raw)
In-Reply-To: <858xgywml9.fsf@lola.goethe.zz>
On 12/23/06, David Kastrup <dak@gnu.org> wrote:
> "Ken Manheimer" <ken.manheimer@gmail.com> writes:
>
> > my allout encryption provisions are badly disrupted with the new pgg
> > revision, when gpg-agent is active.
>
> [...]
>
> > 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.
>
> I'd like to see Emacs 22 out before we have to update all copyright
> notices to 2007. And I am afraid of a full month certain delay before
> the release. It is bad enough having to fight last-minute changes;
> we'd argue ourselves to exhaustion about last-month changes. "Why, we
> still have a full month for testing" is what I expect to hear then.
>
> So personally I'd really be glad if this could be resolved before your
> hiatus, leaving one less excuse to further delay. That does not mean
> that other reasons for delay might not crop up, but at least there is
> a _chance_ that we'll get this beast out the door at one point of
> time.
i've (just) posted a patch that inhibits pgg's use of gpg-agent within
the scope of a let body where allout does the encryption. i hope it's
applied soon, so i can verify the update while i have some time.
the posted patch is a minimal workaround, though. i suspect something
closer to a fix would be to have pgg not resort to pgg-agent when
passphrases are passed in to it - that might be considered a bug in
the current pgg implementation. that would also give me a path to
incrementally integrating gpg-agent functionality to allout's
encryption - that may never make sense for symmetric keys, but may be
fairly easy to do (without sacrificing current allout encryption
conveniences) for key pair encryption.
--
ken
http://myriadicity.net
next prev parent reply other threads:[~2006-12-23 18:11 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 [this message]
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=2cd46e7f0612231011k10b09b85y140ff04347bd4632@mail.gmail.com \
--to=ken.manheimer@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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).