From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daiki Ueno Newsgroups: gmane.emacs.devel Subject: Re: GPGME Date: Wed, 29 Jun 2011 22:15:02 +0900 Message-ID: <87ei2ckcdl.fsf-ueno@unixuser.org> References: <87tycamhmv.fsf@lifelogs.com> <87pqmxvfoh.fsf@lifelogs.com> <87sjrttwh8.fsf@lifelogs.com> <87wrh4b9h9.fsf@lifelogs.com> <87aae05l8p.fsf-ueno@unixuser.org> <87k4d4b66p.fsf@lifelogs.com> <87wrh0fh4g.fsf_-_@lifelogs.com> <87y60ncma8.fsf_-_@lifelogs.com> <87vcvrne02.fsf-ueno@unixuser.org> <87r56ep3sm.fsf@lifelogs.com> <874o39n171.fsf-ueno@unixuser.org> <87iprosxlk.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1309362661 19476 80.91.229.12 (29 Jun 2011 15:51:01 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 29 Jun 2011 15:51:01 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 29 17:50:57 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Qbx2X-0007sY-HU for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2011 17:50:57 +0200 Original-Received: from localhost ([::1]:46927 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qbx2V-0001B4-Q4 for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2011 11:50:55 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:45252) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qbubs-0008PR-MF for emacs-devel@gnu.org; Wed, 29 Jun 2011 09:15:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qbubo-0005Sh-95 for emacs-devel@gnu.org; Wed, 29 Jun 2011 09:15:16 -0400 Original-Received: from ivory4.scn-net.ne.jp ([219.117.176.192]:39236) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1Qbubn-0005SF-Kv for emacs-devel@gnu.org; Wed, 29 Jun 2011 09:15:12 -0400 Original-Received: from ([192.168.0.187]) (envelope sender: ) by ivory4.scn-net.ne.jp with Active!Hunter esmtp server; Wed, 29 Jun 2011 22:15:06 +0900 Original-Received: Received: from well-done.deisui.org (g187018.scn-net.ne.jp [202.83.187.18]) (authenticated) by blue17.scn-net.ne.jp (unknown) with ESMTP id p5TDF43n000942 for ; Wed, 29 Jun 2011 22:15:06 +0900 In-Reply-To: <87iprosxlk.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 29 Jun 2011 06:09:27 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-Received-From: 219.117.176.192 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:141177 Archived-At: Ted Zlatanov writes: > DU> I remember that the problem of encrypt.el was that the data format is > DU> not interoperable and the algorithm used is not interchangeable though > DU> the API might be neutral. > > Is that a problem, if the intent is to provide an Emacs facility? The benefit using the standard GPG format is that it embeds what algorithm is used in data. If Emacs provides bare cipher algorithms, someone may write encryption routines with their own format which won't be interoperable - that is a problem I think. For my case, I had used GPass http://gpass.sourceforge.net as my password manager (currently unmaintained). It turned out that it used bare Blowfish internally and I had to write a script to salvage my password data. > I'm asking if, instead of a new package, we can use `epg-encrypt-string' > to provide symmetric encryption without calling GPG externally. It can > provide it in any format and with any symmetric cipher you think would > make sense. But if you don't think so, then we need a new package to > provide that functionality. I don't care about it. Regards, -- Daiki Ueno