From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, rms@gnu.org, jas@extundo.com
Subject: Re: lisp/url/url-https.el
Date: 12 Apr 2004 00:49:30 -0400 [thread overview]
Message-ID: <m1n05h7qni.fsf-monnier+emacs@empanada.iro.umontreal.ca> (raw)
In-Reply-To: <x58yh1esfw.fsf@lola.goethe.zz>
>> 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
next prev parent reply other threads:[~2004-04-12 4:49 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 21:14 lisp/url/url-https.el Simon Josefsson
2004-04-08 14:57 ` lisp/url/url-https.el Richard Stallman
2004-04-08 15:21 ` lisp/url/url-https.el David Kastrup
2004-04-09 22:44 ` lisp/url/url-https.el Richard Stallman
2004-04-09 23:03 ` lisp/url/url-https.el David Kastrup
2004-04-10 0:17 ` lisp/url/url-https.el Miles Bader
2004-04-12 3:51 ` lisp/url/url-https.el Richard Stallman
2004-04-10 14:41 ` lisp/url/url-https.el Stefan Monnier
2004-04-10 18:41 ` lisp/url/url-https.el Kim F. Storm
2004-04-12 3:52 ` lisp/url/url-https.el Richard Stallman
2004-04-13 10:47 ` lisp/url/url-https.el Mario Lang
2004-04-14 18:02 ` lisp/url/url-https.el Richard Stallman
2004-04-14 18:15 ` lisp/url/url-https.el Ted Zlatanov
2004-04-14 22:09 ` lisp/url/url-https.el Stefan Monnier
2004-04-14 23:42 ` lisp/url/url-https.el Simon Josefsson
2004-04-15 13:42 ` lisp/url/url-https.el Stefan Monnier
2004-04-15 15:30 ` lisp/url/url-https.el Ted Zlatanov
2004-04-16 18:08 ` lisp/url/url-https.el Richard Stallman
2004-04-16 19:18 ` lisp/url/url-https.el Ted Zlatanov
2004-04-15 15:50 ` lisp/url/url-https.el Simon Josefsson
2004-04-15 15:38 ` lisp/url/url-https.el Ted Zlatanov
2004-04-16 18:08 ` lisp/url/url-https.el Richard Stallman
2004-04-16 19:15 ` lisp/url/url-https.el Ted Zlatanov
2004-04-17 8:32 ` lisp/url/url-https.el Eli Zaretskii
2004-04-21 15:33 ` lisp/url/url-https.el Ted Zlatanov
2004-04-16 20:23 ` lisp/url/url-https.el Kai Grossjohann
2004-04-17 6:07 ` lisp/url/url-https.el Ted Zlatanov
2004-04-17 17:14 ` lisp/url/url-https.el Stefan Monnier
2004-04-17 18:28 ` lisp/url/url-https.el Kai Grossjohann
2004-04-21 15:31 ` lisp/url/url-https.el Ted Zlatanov
2004-04-17 19:48 ` lisp/url/url-https.el Richard Stallman
2004-04-16 20:52 ` lisp/url/url-https.el Stefan Monnier
2004-04-17 6:18 ` lisp/url/url-https.el Ted Zlatanov
2004-04-17 18:27 ` lisp/url/url-https.el Kai Grossjohann
2004-04-17 18:32 ` lisp/url/url-https.el Kai Grossjohann
2004-04-19 13:57 ` lisp/url/url-https.el Stefan Monnier
2004-04-19 14:04 ` lisp/url/url-https.el Kai Grossjohann
2004-04-19 15:34 ` lisp/url/url-https.el Stefan Monnier
2004-04-19 20:49 ` lisp/url/url-https.el Kai Grossjohann
2004-04-19 21:05 ` lisp/url/url-https.el Stefan Monnier
2004-04-20 6:38 ` lisp/url/url-https.el Kai Grossjohann
2004-04-20 12:45 ` lisp/url/url-https.el Michael Albinus
2004-04-20 14:20 ` lisp/url/url-https.el Kai Grossjohann
2004-04-20 8:12 ` Checkout a branch in cvs-tree Masatake YAMATO
2004-08-20 20:56 ` Stefan Monnier
2004-08-21 11:44 ` Masatake YAMATO
2004-08-22 1:12 ` Stefan Monnier
2004-04-12 3:52 ` lisp/url/url-https.el Richard Stallman
2004-04-12 4:22 ` lisp/url/url-https.el David Kastrup
2004-04-12 4:49 ` Stefan Monnier [this message]
2004-04-12 10:30 ` lisp/url/url-https.el David Kastrup
2004-04-12 9:54 ` lisp/url/url-https.el Simon Josefsson
2004-04-13 17:45 ` lisp/url/url-https.el Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1n05h7qni.fsf-monnier+emacs@empanada.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=jas@extundo.com \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).