9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Secure ftp Again
Date: Sun,  3 Apr 2005 19:20:05 -0400	[thread overview]
Message-ID: <ee9e417a0504031620749edd29@mail.gmail.com> (raw)
In-Reply-To: <186925c4b8718cb5e5e1ce8747f78ce2@collyer.net>

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

since icann has deprecated having separate
"automatically start tls after connecting" tcp ports
for services, tweaking any of these is not very useful.
for example (and this was my point earlier, which
i did not make very clearly) in ftp you have to
send an "AUTH TLS" and have the server send back
a success response before you start tls.  other
protocols have similar protocol-specific negotiation
phases.

also, adding it to cs requires having /net/tcp understand
the !tls qualifier (cs just passes !r into the tcp dial string),
which would mean having the gory public-key certificate
etc. part of tls in the kernel (or in a separate user-space
network stack).

russ


  reply	other threads:[~2005-04-03 23:20 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 [this message]
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
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=ee9e417a0504031620749edd29@mail.gmail.com \
    --to=russcox@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).