From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>,
lucio@proxima.alt.za
Subject: Re: [9fans] Secure ftp Again
Date: Sun, 3 Apr 2005 18:17:14 -0800 [thread overview]
Message-ID: <67CB8264D4E6B1F8F444DEA6@peregrin.orthanc.ca> (raw)
In-Reply-To: <186925c4b8718cb5e5e1ce8747f78ce2@collyer.net>
--On 2005-4-3 4:05 PM -0700 geoff@collyer.net wrote:
> If one were going to add TLS dialing as a standard facility, I'd
> suggest adding it to cs, not dial, perhaps as a qualifier similar to
> "!r": tcp!host!ftp!tls. This would make TLS dialing available
> uniformly and immediately to all programs, without recompilation, and
> even to command-line usage.
But the trend is towards negotiating TLS after chatting over the
connection a bit. IMAP, SMTP, and POP all have a separate command to
start up TLS. (Yes, there is an unofficial "imaps" that I expect to
slowly die out now that RFC3501 has made STARTTLS mandatory to
implement.)
So adding "...!tls" to cs doesn't really solve the general case.
--lyndon
next prev parent reply other threads:[~2005-04-04 2:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 23:11 Gregory Pavelcak
2005-04-03 3:05 ` Russ Cox
2005-04-03 5:05 ` lucio
2005-04-03 13:36 ` Russ Cox
2005-04-03 13:40 ` Devon H. O'Dell
2005-04-03 13:47 ` Russ Cox
2005-04-03 14:17 ` lucio
2005-04-03 23:05 ` geoff
2005-04-03 23:20 ` Russ Cox
2005-04-03 23:57 ` geoff
2005-04-04 1:05 ` geoff
2005-04-04 4:02 ` lucio
2005-04-04 11:57 ` Russ Cox
2005-04-04 2:17 ` Lyndon Nerenberg [this message]
2005-04-04 3:01 ` Micah Stetson
2005-04-04 4:12 ` lucio
2005-04-04 4:32 ` geoff
2005-04-04 11:09 ` C H Forsyth
2005-04-04 11:37 ` boyd, rounin
2005-04-04 11:51 ` Russ Cox
2005-04-04 23:40 ` geoff
2005-04-04 18:56 ` Tim Newsham
2005-04-03 21:06 ` Christoph Lohmann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67CB8264D4E6B1F8F444DEA6@peregrin.orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@cse.psu.edu \
--cc=lucio@proxima.alt.za \
/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.
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 NNTP newsgroup(s).