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: new version of allout.el - patch and ChangeLog Date: Sat, 1 Oct 2005 12:28:17 -0400 Message-ID: <2cd46e7f0510010928v8244052k2a98375e38fdd2ed@mail.gmail.com> References: <2cd46e7f0509301024r71462d81v81ebd8e858f06305@mail.gmail.com> <20050930210649.GA22126@kenny.sha-bang.local> <2cd46e7f0509301452l72c262d6l89efd6fb772f61b2@mail.gmail.com> 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 1128184743 30120 80.91.229.2 (1 Oct 2005 16:39:03 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 1 Oct 2005 16:39:03 +0000 (UTC) Cc: Sascha Wilde , Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 01 18:39:01 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ELkNa-0007kY-MM for ged-emacs-devel@m.gmane.org; Sat, 01 Oct 2005 18:38:31 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ELkNa-0007nu-27 for ged-emacs-devel@m.gmane.org; Sat, 01 Oct 2005 12:38:30 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ELkMM-0007Lg-Vx for emacs-devel@gnu.org; Sat, 01 Oct 2005 12:37:15 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ELkMI-0007KI-Nq for emacs-devel@gnu.org; Sat, 01 Oct 2005 12:37:12 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ELkMH-0007EV-HR for emacs-devel@gnu.org; Sat, 01 Oct 2005 12:37:09 -0400 Original-Received: from [64.233.162.196] (helo=zproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ELkDi-0004zV-96 for emacs-devel@gnu.org; Sat, 01 Oct 2005 12:28:18 -0400 Original-Received: by zproxy.gmail.com with SMTP id k1so83448nzf for ; Sat, 01 Oct 2005 09:28:17 -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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hUsftb/oDJJHjoZtJD6YiGAhhPufuRhM7AQ/Jj9oPwWgFMrmn1+sJvfqwFPhRB1jY2owiXa4qr9ZSOdCOEqThOg6Z3wOQvZTNNdocQcIeIsl2LfkdEdSyKqQIvOi1cdNlgYajrsdli6ahYKpkxTFLmoE9WSf0fb2uyZJssMAfgA= Original-Received: by 10.36.34.15 with SMTP id h15mr95270nzh; Sat, 01 Oct 2005 09:28:17 -0700 (PDT) Original-Received: by 10.36.36.6 with HTTP; Sat, 1 Oct 2005 09:28:17 -0700 (PDT) Original-To: emacs-devel@gnu.org In-Reply-To: <2cd46e7f0509301452l72c262d6l89efd6fb772f61b2@mail.gmail.com> 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:43430 Archived-At: On 9/30/05, Ken Manheimer wrote: > On 9/30/05, Sascha Wilde wrote: > > On Fri, Sep 30, 2005 at 01:24:14PM -0400, Ken Manheimer wrote: > > [...] > > > topic encryption functionality depends on both mailcrypt an= d > > > crypt++ packages. (non-encryption allout functionality is = not > > > disrupted if either mailcrypt or crypt++ are absent.) > > > > why do you relay on these packages, which aren't part of gnu emacs, > > when we have pgg? > > good question - i wasn't aware of pgg. can you tell me more about it? > i'd be very happy to find a single package that cleanly provides the > encryption interface that allout needs! andreas pointed me at pgg's bundling in gnus, for which gentoo has an ebuild. i emerged it and got access to gpp and the info file. it looks nice - clean - but appears to have the same drawback, for my purposes, as mailcrypt. it will decrypt messages encoded with a symmetric key, but provides no api for encrypting with a symmetric key. that lack is a show-stopper for my purposes. that mailcrypt and pgg would concentrate on public-key mode makes a lot of sense, considering the ultimate purpose is encryption and/or signing of messages to be exchanged between remote parties - email, news, software packaging, etc. my primary concern for encryption in allout is with conveniently securing notes for oneself. the lattitude of symmetric keys offers much better convenience in that context. i actually inquired on the mailcrypt developers list about the lack of provision for symmetric-key encryption, and the general concensus was that it just was an oversight, not a deliberate avoidance. i presume (as i suggest above) because it's not useful for the message-exchange realm. it may well be that pgg is preferable, somehow, to mailcrypt - they both offer similar functionality, including key caching, as well as the lack of an interface for encrypting with a symmetric key. but the changeover won't gain me anything i can yet see - i'll still need to also use crypt++ for the symmetric key encoding. and the cost in effort of switching from working code would not be trivial, so until/unless i see a compelling gain, or someone else does the integration (and convinces me that pgg is more widespread than mailcrypt), i'm think i'm fine with mailcrypt. ken ken.manheimer@gmail.com