From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Daiki Ueno" Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: encrypt.el in No Gnus 0.7 Date: Fri, 2 Nov 2007 00:24:04 +0900 Message-ID: <54a15d860711010824w6888aafdgb0a0e5d48f6fdebb@mail.gmail.com> 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=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1193930669 26142 80.91.229.12 (1 Nov 2007 15:24:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 1 Nov 2007 15:24:29 +0000 (UTC) To: "Daiki Ueno" , emacs-devel@gnu.org, ding@gnus.org, "Miles Bader" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 01 16:24:32 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1InbuD-0004eZ-9U for ged-emacs-devel@m.gmane.org; Thu, 01 Nov 2007 16:24:25 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Inbu3-0002Af-7A for ged-emacs-devel@m.gmane.org; Thu, 01 Nov 2007 11:24:15 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Inbtz-0002AD-G5 for emacs-devel@gnu.org; Thu, 01 Nov 2007 11:24:11 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Inbty-00027x-0C for emacs-devel@gnu.org; Thu, 01 Nov 2007 11:24:10 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Inbtx-00026z-Rf for emacs-devel@gnu.org; Thu, 01 Nov 2007 11:24:09 -0400 Original-Received: from ug-out-1314.google.com ([66.249.92.168]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Inbtw-0002Ug-MU for emacs-devel@gnu.org; Thu, 01 Nov 2007 11:24:09 -0400 Original-Received: by ug-out-1314.google.com with SMTP id a2so528240ugf for ; Thu, 01 Nov 2007 08:24:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=5WPI8XPbUshtzsFJAB4wlNSInnMJFrhPD6DI9qO/RxU=; b=hKVeUgWyhdwEuyfV34kgt84+WzhjosYmq07LhoxLi1pWmeW1bGvLMv8Gm1GK0sV5X0+WDBymXaQ3dMnK2LsRzb0/byk00fBanAAiKXx2EBayiE3XA4ykWegJltrC1JMg4d1hHThI912t9j2DVhAeyRUNAuwCdt+v6Ampp4oCths= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=AEwlUUf2V4Yqse5Qb4rbkmXjd+IzseqAvyTax1QuoWYo3b1T4+ehXC3hgWsnqRHA8ULO+/K+xTJojqAPt5R0bDXlrBi6rz+/UBh4UGBnSOEYA4XExXGauPmEWDql+X3rkadiB++S5LF3kfTibQ7k/YzXMviiBylHSljDzfSrPVM= Original-Received: by 10.142.226.2 with SMTP id y2mr149574wfg.1193930644362; Thu, 01 Nov 2007 08:24:04 -0700 (PDT) Original-Received: by 10.142.213.14 with HTTP; Thu, 1 Nov 2007 08:24:04 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-Google-Sender-Auth: 78e0672ab517921c X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) 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:82297 gmane.emacs.gnus.general:65521 Archived-At: 2007/11/2, Ted Zlatanov : > On Thu, 1 Nov 2007 10:30:54 +0900 "Daiki Ueno" wrote: > 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. I think encrypt-file-alist is too much custamisable since GnuPG records what cipher is used to encrypt in the PGP message. See RFC2440. > 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. Yes, EasyPG does not (yet) provide a way to specify the cipher algorithm but as I mentioned above we need to specify only the first time. Is it not enough to edit ~/.gnupg/gpg.conf or manually call the gpg command with options? I also think that your XOR cipher is not a good idea as a fallback algorithm. Have you ever read Simon Singh's "The Code Book"? > 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. epa-file.el is an *application* not a *libarary* (I'm a bit tired of explanating these difference again and again...). epg.el is the library and it provides the API. Since it only accepts string or file for encryption and do not cache passphrase, it is simpler than encrypt.el. Regards, -- Daiki Ueno