From: Christoph Lohmann <20h@r-36.net>
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 23:06:39 +0200 [thread overview]
Message-ID: <20050403230639.117800a3.20h@r-36.net> (raw)
In-Reply-To: <64b70cf896f7dd37633fd9d5e7dfca94@comcast.net>
Good evening.
On Sat, 2 Apr 2005 18:11:59 -0500
Gregory Pavelcak <g.pavelcak@comcast.net> wrote:
> A couple of weeks ago, I posted saying that I couldn't connect
> to an ftp server. I got the message "No non-SSL connections
> allowed" (Or something like that). I said that I had looked at
> ssl(3), but couldn't see how to use it.
>
> Someone (Russ Cox???. I forget now.) replied saying that I
> probably needed to be looking at tls and pushtls. Well, I have.
> I hate to be a bonehead about this, but I still don't see how
> to make use of these things. The tips pages have nice things
> for ordinary users like mounting cds and using cdfs. Would
> anyone be kind enough to walk me through making secure
> ftp connections in a `tip o' the day' sort of way.
>
> Thanks.
>
> Greg
I submitted a patch (/n/sources/patch/ftpfs-auth-tls), which adds
the option -t for AUTH TLS to ftpfs. It seems to be what you need,
if the server you want to connect to supports TLSv1 or SSLv3.
Sincerly,
Christoph
prev parent reply other threads:[~2005-04-03 21:06 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
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 [this message]
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=20050403230639.117800a3.20h@r-36.net \
--to=20h@r-36.net \
--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).