From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general,gmane.emacs.devel Subject: Re: encrypt.el in No Gnus 0.7 Followup-To: gmane.emacs.devel Date: Thu, 01 Nov 2007 10:04:40 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: References: <87zly3y4ru.fsf@catnip.gol.com> <87odejy30k.fsf@catnip.gol.com> <54a15d860710311830s4fa203e3y53fbd6f51496f007@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1193929550 21793 80.91.229.12 (1 Nov 2007 15:05:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 1 Nov 2007 15:05:50 +0000 (UTC) Cc: emacs-devel@gnu.org, ding@gnus.org, "Miles Bader" To: "Daiki Ueno" Original-X-From: ding-owner+M14014@lists.math.uh.edu Thu Nov 01 16:05:52 2007 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1InbcC-0006Pf-1j for ding-account@gmane.org; Thu, 01 Nov 2007 16:05:48 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1Inbbq-0003bt-6X; Thu, 01 Nov 2007 10:05:26 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Inbbo-0003be-Tt for ding@lists.math.uh.edu; Thu, 01 Nov 2007 10:05:24 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.67) (envelope-from ) id 1Inbbi-0006cl-Hm for ding@lists.math.uh.edu; Thu, 01 Nov 2007 10:05:24 -0500 Original-Received: from blockstar.com ([170.224.69.95] helo=mail.blockstar.com) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1Inbbb-0007WQ-00 for ; Thu, 01 Nov 2007 16:05:11 +0100 Original-Received: from tzz (c-67-186-103-18.hsd1.il.comcast.net [67.186.103.18]) by mail.blockstar.com (Postfix) with ESMTP id 0B07D3F850D; Thu, 1 Nov 2007 08:25:37 -0700 (PDT) X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6;d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Followup-To: "Daiki Ueno" , emacs-devel@gnu.org, ding@gnus.org, "Miles Bader" In-Reply-To: <54a15d860710311830s4fa203e3y53fbd6f51496f007@mail.gmail.com> (Daiki Ueno's message of "Thu, 1 Nov 2007 10:30:54 +0900") User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1.50 (darwin) X-Spam-Score: -2.6 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:65520 gmane.emacs.devel:82296 Archived-At: On Thu, 1 Nov 2007 10:30:54 +0900 "Daiki Ueno" wrote: DU> 2007/11/1, Ted Zlatanov : >> It definitely makes sense to move encrypt.el into Emacs as well then. >> My main concern was that it overlaps with all the other *crypt*.el >> packages, and I really think that encrypt.el's simplicity and >> non-invasiveness justifies its existence. But it requires password.el. >> I'm open to suggestions as to the best way to manage it. DU> epa-file.el in EasyPG can also do that. Have you looked at it? DU> I think it is much easier to use since it does not need elisp setup DU> like encrypt-file-alist. encrypt-file-alist can be set up via Customize. It's intended as an API, however, so I am not concerned about end users too much. Your EasyPG code is probably better, I am not an ELisp expert by any means. But epa-file.el not an API, and does not support arbitrary ciphers as encrypt.el does (AFAIK). See the encrypt.el XOR cipher for an example of what I mean. EasyPG seems firmly attached to the GPG/PGP process, which is not a bad thing, only it doesn't provide an abstract encryption API. DU> Yes, EasyPG is a bit complex and invasive. But IMO sometimes DU> usability should be given priority over simplicity & DU> non-invasiveness. Sure, and that's your choice to make within the EasyPG package, which has specific needs. I think an API must be simple an non-invasive, though, and encrypt.el is by those standards a better API than epa-file.el or any other *crypt* package I've seen. If I'm wrong, please tell me. DU> BTW, I just tried encrypt.el and I encountered a few issues. (1) It DU> uses gnus-error to report errors so there is a dependency to DU> gnus-util.el. Yes. I'll gladly fix that if it moves outside Gnus but for now that's the appropriate notification mechanism. DU> (2) The instruction says M-x encrypt-file-contents but there is no DU> such function (perhaps is it a typo of DU> encrypt-write-file-contents?). I fixed that in the docs. Thank you very much. DU> (3) encrypt-find-model does not resolve path names. That was intentional at the time, because I thought resolving the path wouldn't allow matching ~ and such. If it's wrong, please let me know. Ted