From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Ken Manheimer" Newsgroups: gmane.emacs.devel Subject: Re: Documenting gpg-agent Date: Sat, 23 Dec 2006 13:11:17 -0500 Message-ID: <2cd46e7f0612231011k10b09b85y140ff04347bd4632@mail.gmail.com> References: <2cd46e7f0612230904s7059393co2ed34a756775ee84@mail.gmail.com> <858xgywml9.fsf@lola.goethe.zz> NNTP-Posting-Host: dough.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1166897501 5403 80.91.229.10 (23 Dec 2006 18:11:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 23 Dec 2006 18:11:41 +0000 (UTC) Cc: Sascha Wilde , rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 23 19:11:40 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by dough.gmane.org with esmtp (Exim 4.50) id 1GyBLM-0002tk-QE for ged-emacs-devel@m.gmane.org; Sat, 23 Dec 2006 19:11:37 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GyBLM-0008QQ-5O for ged-emacs-devel@m.gmane.org; Sat, 23 Dec 2006 13:11:36 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GyBL8-0008Pn-Ax for emacs-devel@gnu.org; Sat, 23 Dec 2006 13:11:22 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GyBL5-0008NY-FR for emacs-devel@gnu.org; Sat, 23 Dec 2006 13:11:21 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GyBL5-0008NS-A5 for emacs-devel@gnu.org; Sat, 23 Dec 2006 13:11:19 -0500 Original-Received: from [64.233.182.185] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GyBL4-0000Ph-SW for emacs-devel@gnu.org; Sat, 23 Dec 2006 13:11:19 -0500 Original-Received: by nf-out-0910.google.com with SMTP id d4so3786892nfe for ; Sat, 23 Dec 2006 10:11:17 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nZvCdLNcFXHzilFj3++E1aTw+Cj5LJOXfV+cmeZokuQMKpw1m9vo6lcw5yBOepaCubsy+Pahn/q2k/g2taKPZI9oZi4MaUp2o21Xg1UzXLVAK1WxOlQNATwAldhlyWLNWpOqNrNtY6SQ4UQBgmyNl4YuKS49bnWtNdLPsp49yCg= Original-Received: by 10.78.201.15 with SMTP id y15mr2280829huf.1166897477225; Sat, 23 Dec 2006 10:11:17 -0800 (PST) Original-Received: by 10.78.198.10 with HTTP; Sat, 23 Dec 2006 10:11:17 -0800 (PST) Original-To: "David Kastrup" In-Reply-To: <858xgywml9.fsf@lola.goethe.zz> Content-Disposition: inline X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:64164 Archived-At: On 12/23/06, David Kastrup wrote: > "Ken Manheimer" 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