From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sun,  3 Apr 2005 18:17:14 -0800
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
Message-ID: <67CB8264D4E6B1F8F444DEA6@peregrin.orthanc.ca>
In-Reply-To: <186925c4b8718cb5e5e1ce8747f78ce2@collyer.net>
References: <186925c4b8718cb5e5e1ce8747f78ce2@collyer.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 
Topicbox-Message-UUID: 324321d6-ead0-11e9-9d60-3106f5b1d025

--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