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: pgg symmetric encryption patch Date: Wed, 5 Oct 2005 15:16:21 -0400 Message-ID: <2cd46e7f0510051216o5a9d5aadycd74ac089ccfca5b@mail.gmail.com> References: <2cd46e7f0509301024r71462d81v81ebd8e858f06305@mail.gmail.com> <20050930210649.GA22126@kenny.sha-bang.local> <2cd46e7f0509301452l72c262d6l89efd6fb772f61b2@mail.gmail.com> <2cd46e7f0510010928v8244052k2a98375e38fdd2ed@mail.gmail.com> <20051002104823.GA31722@kenny.sha-bang.local> <20051003192503.GA15503@kenny.sha-bang.local> <2cd46e7f0510031250u66ea1349yb437d539ce4027ef@mail.gmail.com> <20051004105330.GA5288@kenny.sha-bang.local> <20051005161905.GA6208@kenny.sha-bang.local> Reply-To: Ken Manheimer NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1128540060 20891 80.91.229.2 (5 Oct 2005 19:21:00 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 5 Oct 2005 19:21:00 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 05 21:20:55 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ENEmf-0001sb-IH for ged-emacs-devel@m.gmane.org; Wed, 05 Oct 2005 21:18:33 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ENEme-0005e9-QJ for ged-emacs-devel@m.gmane.org; Wed, 05 Oct 2005 15:18:32 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ENElh-00058A-73 for emacs-devel@gnu.org; Wed, 05 Oct 2005 15:17:33 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ENEkg-0004aK-1d for emacs-devel@gnu.org; Wed, 05 Oct 2005 15:16:39 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ENEkZ-0004Yd-FR for emacs-devel@gnu.org; Wed, 05 Oct 2005 15:16:23 -0400 Original-Received: from [64.233.162.206] (helo=zproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ENEkZ-0007Bd-1H for emacs-devel@gnu.org; Wed, 05 Oct 2005 15:16:23 -0400 Original-Received: by zproxy.gmail.com with SMTP id k1so153588nzf for ; Wed, 05 Oct 2005 12:16:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=R8ZYSzyFtsZ19RZHWyGF67fXU4XO71qNnOEx0vpSkj90uqT8XvCb4WKaLqZFVUj3axvxP1JNjQ77Xk2WPmHxyvT4ywdL13dny8DfnJeBeTFLGasItNTU+w73leMCKNVH3ADOMaJh5xPuf95DVekSzqpwSp5xd5ErmP31jHqI0dc= Original-Received: by 10.37.22.80 with SMTP id z80mr891993nzi; Wed, 05 Oct 2005 12:16:21 -0700 (PDT) Original-Received: by 10.36.36.11 with HTTP; Wed, 5 Oct 2005 12:16:21 -0700 (PDT) Original-To: Ken Manheimer , "Richard M. Stallman" , schwab@suse.de, emacs-devel@gnu.org, ueno@unixuser.org In-Reply-To: <20051005161905.GA6208@kenny.sha-bang.local> 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:43587 Archived-At: On 10/5/05, Sascha Wilde wrote: > On Tue, Oct 04, 2005 at 12:53:30PM +0200, Sascha Wilde wrote: > > > I'll try to find the time to make this a proper feature of pgg. (I > > also added the original author to the cc, so he might add his > > thoughts) > > I attached a more complete patch, including documentation and > changelog entries. > > Any comments, bug-fixes, flames are highly appreciated. i have some questions regarding my switching allout over to use pgg.=20 i've been looking over the impact, and it's complicated by the intricate way i use mailcrypt's key caching mechanism. i would have to change pgg's key caching stuff to enable me, for instance, to query for the presence of a key, and also change the encryption/decryption function signatures to take explictly passed-in keys. it will not be trivial, and i don't want to launch into the work if there's no chance the pgg changes will be accepted. i know there's no way in advance to know whether my changes will or won't be acceptible, but i would like to know whether there will be attention available to evaluate them and the possibility that they'll be accepted? my time frame is also a little daunting - i think i have at least a few days of work, and am going to be away for a week in the middle of next week, so may not have anything finished until a few weeks from now. any thoughts? ken manheimer ken.manheimer@gmail.com