From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: lisp/url/url-https.el Date: 12 Apr 2004 00:49:30 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1081745456 31044 80.91.224.253 (12 Apr 2004 04:50:56 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 12 Apr 2004 04:50:56 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, jas@extundo.com Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Apr 12 06:50:46 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 1BCtPC-0004dU-00 for ; Mon, 12 Apr 2004 06:50:46 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BCtPC-0000iK-00 for ; Mon, 12 Apr 2004 06:50:46 +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 1BCsSN-0004XI-OY for emacs-devel@quimby.gnus.org; Sun, 11 Apr 2004 23:49:59 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BCsRz-0004WM-7o for emacs-devel@gnu.org; Sun, 11 Apr 2004 23:49:35 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BCsRx-0004V8-Sl for emacs-devel@gnu.org; Sun, 11 Apr 2004 23:49:34 -0400 Original-Received: from [206.47.199.165] (helo=simmts7-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BCsRv-0004QO-SS; Sun, 11 Apr 2004 23:49:31 -0400 Original-Received: from empanada.local ([67.70.165.72]) by simmts7-srv.bellnexxia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040412044928.OIS13427.simmts7-srv.bellnexxia.net@empanada.local>; Mon, 12 Apr 2004 00:49:28 -0400 Original-Received: by empanada.local (Postfix, from userid 502) id 16E59153C50; Mon, 12 Apr 2004 00:49:31 -0400 (EDT) Original-To: David Kastrup In-Reply-To: Original-Lines: 32 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 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:21509 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21509 >> Are url-https.el and ssl.el really specifically designed to call >> encryption routines? I thought they only run some external communication >> program which happens to use encryption. >> >> I am not sure whether this makes a difference. I had better get legal >> advice about this. Could someone describe for me the overall >> structure of the situation, so I can ask about it? >> >> Much like Tramp. >> >> I don't know this case and the Tramp case are similar in the way >> that matters legally. > tramp can call ssh, but ssh can also connect using plain unencrypted > rsh. So it would depend on the configuration of ssh whether a > connection is encrypted or not. Every case is unique, of course, but AFAIK, Tramp weas mostly written to use SSH rather than FTP because SSH is secure thanks to authentication and encryption. Yes, you can use it with rsh, with su, etc, which do not use encryption, but RMS's poiint was that ssl.el was written specifically for encryption and I thought Tramp was pretty close in that respect. The way I see it ssl.el does not fall under the law because its purpose has nothing to do with encryption. It is just designed to connect to some hosts using some particular protocol (not because this protocol is encrypted but because some hosts require this protocol for some of their operations) by running some external program which does all the socket-setup, protocol negotiation, etc... the encryption is actually pretty minor in this respect. Stefan