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 08:47:27 -0500 [thread overview]
Message-ID: <ee9e417a05040306471caf9d29@mail.gmail.com> (raw)
In-Reply-To: <20050403134016.GP92880@smp500.sitetronics.com>
> > changing dial? no. writing a tlsdial?
> > maybe, but it doesn't happen very often.
> > what's more common is that you connect,
> > talk plaintext for a little while, and then decide
> > to start tls. i don't think there are enough
> > instances yet to know what the common case is.
> >
> > russ
>
> It seems to be pretty standard protocol to me. Exchange, verify,
> encrypt. The original IETF draft is at
i was talking about tls, not the ftp tls.
i agree that the tls ftp looks standard,
but i don't know of any ftp servers that
actually implement it (or why they would!)
so i have nothing to test against.
i also don't understand how much auth
is supposed to happen before you start tls.
it's all a little weird.
> and every current popular FTP client implements it, so there
> should be plenty of source with a friendly license out there.
i'm not worried about this either. it's only a
couple of lines of code. no need to copy
someone else.
russ
next prev parent reply other threads:[~2005-04-03 13:47 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 [this message]
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
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=ee9e417a05040306471caf9d29@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).