I'm not sure about how to secure this. Make a special account seperate from
my normal one just for FTP'ing and heavily restrict it? Of course disallow
anonymous connections... Require the password on the special account be
changed frequently? Set the special user's shell interpreter to something
like /dev/null (how do you do it so it just immediately kicks them off?)
I would like to store files and backups and such on the remote server, but
it just seems too insecure. Is there possibly a way to tunnel an ftp
connection through ssh? How would that be done?
Thanks for any insight to a novice
Luke
> I would like to store files and backups and such on the remote server, but
> it just seems too insecure. Is there possibly a way to tunnel an ftp
> connection through ssh? How would that be done?
man scp
--
AngryBob
Who is this girl and why is she wearing my pants!?!?
--Nick Black (from right behind me)
> What would you like to read? [LLoe...@home.com or ?*]
> this is a Luke scroll! it says:
>
> > I would like to store files and backups and such on the remote server,
> > but it just seems too insecure. Is there possibly a way to tunnel an
> > ftp connection through ssh? How would that be done?
>
> man scp
A variation that I think you'll find more flexible, btw, and better suited
to generating backups straight to remote tape:
here# find /data -mtime -1 ! -name \*.bak | cpio -H tar -ov \
| ssh -i ~/.ssh/backup backup@there "cat >> /dev/tape"
That way the `backup' identity can have no passphrase if that's what you
want, but obviously it must be tied to a specific IP# on `there'. But at
least you get to do it all with a pipe and can specify whatever criteria
you like with `find'.
~Tim
--
It's all over the front page |pig...@glutinous.custard.org
You give me road rage |http://piglet.is.dreaming.org
Racing through the best days |