From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: lisp/url/url-https.el Date: Sat, 17 Apr 2004 02:18:59 -0400 Organization: =?koi8-r?q?=F4=C5=CF=C4=CF=D2=20=FA=CC=C1=D4=C1=CE=CF=D7?= @ Cienfuegos Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <4nvfjzazzg.fsf@lifelogs.com> References: <87fzb8cfxq.fsf@lexx.delysid.org> <4nvfk2whna.fsf@lifelogs.com> <87vfk28bl0.fsf-monnier+emacs@gnu.org> <4n1xmpi747.fsf@b2-25-3.bwh.harvard.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1082183680 397 80.91.224.253 (17 Apr 2004 06:34:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 17 Apr 2004 06:34:40 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat Apr 17 08:34:34 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BEjPO-0000RY-00 for ; Sat, 17 Apr 2004 08:34:34 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BEjPN-00024x-00 for ; Sat, 17 Apr 2004 08:34:34 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BEjPI-00084O-Ag for emacs-devel@quimby.gnus.org; Sat, 17 Apr 2004 02:34:28 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BEjOx-0007kY-3M for emacs-devel@gnu.org; Sat, 17 Apr 2004 02:34:07 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BEjOF-0006UG-Ct for emacs-devel@gnu.org; Sat, 17 Apr 2004 02:33:56 -0400 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BEjOD-0006QI-Mt for emacs-devel@gnu.org; Sat, 17 Apr 2004 02:33:21 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BEjOD-00025U-00 for ; Sat, 17 Apr 2004 08:33:21 +0200 Original-Received: from asimov.bwh.harvard.edu ([134.174.9.63]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 17 Apr 2004 08:33:20 +0200 Original-Received: from tzz by asimov.bwh.harvard.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 17 Apr 2004 08:33:20 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 43 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: asimov.bwh.harvard.edu 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" User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:ex2k4/3yY+4/akFp9Pi97U2a8JM= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:21808 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21808 On 16 Apr 2004, monnier@iro.umontreal.ca wrote: >>> Can't we write a generic "auto-decrypt-mode" which works similarly >>> to auto-compress-mode (or maybe even a patch to auto-compress-mode >>> which allows "compression using gpg") ? This package wouldn't be >>> distributable with Emacs but it doesn't have anything specific to >>> do with Gnus and can distributed separately (e.g. from a non-US >>> location). > >> crypt++.el does that. > > No, it doesn't. auto-compress-mode uses file-name-handler-alist, > whereas crypt++ uses things like find-file-hooks. Sorry, I didn't know. >> I find it intrusive, not to mention that it doesn't play nice with >> many packages (noted as bugs in the comments of crypt++.el). > > Using file-name-handler-alist would make it much less intrusive and > much more reliable (but would require crypted files to have an > easily recognizable name). I think piggybacking on top of Tramp would be best, since it does so much of the work already. >> I feel that, because of the complexity and variety of encryption >> programs and ciphers, a file encryption API is better than the >> crypt++.el approach. > > I agree that the implementation technique used by crypt++ is > inappropriate (seems to be inherited from way back, probably a time > when file-name-handlers-alist wasn't available). > > But could you explain what a file encryption API would provide that > can't be obtained directly from file-name-handlers? Well, a file encryption API can always provide the file handlers. The file handlers can't provide the API as easily. An API lets a programmer control every aspect of our operation; file handlers are a semi-automatic layer that's just not as useful to developers. Ted