9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell " <dodell@offmyserver.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Secure ftp Again
Date: Sun,  3 Apr 2005 15:40:16 +0200	[thread overview]
Message-ID: <20050403134016.GP92880@smp500.sitetronics.com> (raw)
In-Reply-To: <ee9e417a050403063622954ccb@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

On Sun, Apr 03, 2005 at 08:36:56AM -0500, Russ Cox wrote:
> > > If so, you need to change ftpfs/hget to pushtls after
> > > connecting:
> > >     TLSconn conn;
> > >     fd = dial(etc.);
> > >     memset(&conn, 0, sizeof conn);
> > >     fd = tlsClient(fd, &conn);
> > > instead of just calling dial.
> >
> > Shouldn't this be done by enhancing dial to understand a TLS
> > qualifier?  How difficult would that be?  I'm a lot better at trivial
> > changes, maybe I can figure my way around it if it makes sense.
> 
> 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

http://www.ford-hutchinson.com/~fh-1-pfh/draft-murray-auth-ftp-ssl-05.txt

and every current popular FTP client implements it, so there
should be plenty of source with a friendly license out there.

--Devon

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

  reply	other threads:[~2005-04-03 13:40 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  [this message]
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
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=20050403134016.GP92880@smp500.sitetronics.com \
    --to=dodell@offmyserver.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).