Very Computer

Although I know that FTP is inherently insecure, I've got to setup an
FTP site to upload content to WWW server (thousands of files).
What is the most secure way/software to do this task? Please also
consider that content authors are not very tech literate and most
of them are using Windows. I know about ftp login over ssh, but for
most of them even that way will be too hard :-/

So here come the requirements:
1) Login must be secured. Content is not that sensitive, only login
information is.
2) There should be an easy way to connect to the server from Windows
machines and upload the content.

What do you guys think? Thanks in advance.

--
"A complex system that works is invariably found to have evolved from a simple
system that worked."
-- John Gall, _Systemantics_

Quote:> Hi folks

> Although I know that FTP is inherently insecure, I've got to setup an
> FTP site to upload content to WWW server (thousands of files).
> What is the most secure way/software to do this task? Please also
> consider that content authors are not very tech literate and most
> of them are using Windows. I know about ftp login over ssh, but for
> most of them even that way will be too hard :-/

> So here come the requirements:
> 1) Login must be secured. Content is not that sensitive, only login
> information is.
> 2) There should be an easy way to connect to the server from Windows
> machines and upload the content.

> What do you guys think? Thanks in advance.

My $2*10-2.

-Arild Jensen

haven't played with scp that much on windoze.

--

[snip]

Quote:> > What about an SCP client for Windows? Since you have to encrypt the
> > login, I mean. Take a look at http://www.freessh.org.

> Or even SecureFX for Windoze. might be better for those more comfortable
> with a very simple windoze environment.

> haven't played with scp that much on windoze.

While you're passing by proper solutions, how's about rsync? Exists for
windoze as well, and will tunnel stuff through ssh nicely if you want.

One word of advice to the OP: don't let a user/password across the 'net in
plaintext if it's valid for a shell login. Use hosts-based access
restrictions on whatever protocol you choose (ie FTP or ssh-based).

~Tim
--
   9:39am  up 23 days, 11:51, 11 users,  load average: 0.00, 0.00, 0.00

http://piglet.is.dreaming.org |Direct-inject pleasure when the going gets tough

Check it out at http://safetp.cs.berkeley.edu

that was *exactly* what I was looking for. I'm most pleasantly
suppriesed on the easyness of installation on client as well as an the
server B-)

pak schrieb:

Quote:

> Have you looked at SafeTP?

> Check it out at http://safetp.cs.berkeley.edu