[LUGSB] Question about FTP.

[JST]

Thank you everyone who responded.

I think in the future when I have this properly set up, I will be using
mostly SSH and it's various applications to do everything securely.  I'm
going to try and figure out how to set it up to use keys instead of
passwords.

But the laptop that was running the FTP server unfortunately was not
mine, and I set up FileZilla Server on it, a nice foss FTP server for
Windows.  I wound up using wget to copy everything from it, which worked
nicely.  "wget -r ftp://anonymous@<ip-of-laptop>" did the trick, when I
was inside the directory that I wanted everything to go to.

On an aside, does anyone else have the same issues with Samba / Windows
networking that I do?  I have never had it work reliably even back when
I used windows, let alone trying to get smbclient to work.  Sometimes
you can share folders on one system and they just refuse to appear on
other windows machines... but eventually do after a few minutes.  The
entire NetBIOS setup just seems flaky to me.  But running an FTP server
on that Windows machine just works flat out.  I will only have to get
this data once, and then host it to the house from my server.  Probably
using SFTP as recommended.

One other question.  Right now, I talk to all of my home computers using
their internal ip address.  Now, in the windows paradigm every system
can be set to use a NetBIOS name, but if I wanted to do something like
that in a UNIX way, I have to run a DNS server right?  So laptop1.home,
desktop3.home, and so on can be used as identifiers?  Or can that be
done without running a DNS server?  They all grab an IP using DHCP, and
so it keeps changing, and is annoying.  So is typing in the dotted
decimal addresses.

Thanks in advance.

Ilya Sukhanov (dotCOMmie) wrote:
> Benjamin Kudria wrote:
>> You can do SSH, certainly, I also like ncftp.  Looking at my bash
>> history, I did:
>> ncftpget -v -T -R -u user ftp.remote.com localdir remotedir
>> You probably want to look up the flags in the man page, however.
> 
> FTP as a protocol is dead. There are very few cases in which you would
> still
> want to use it. For example send a file to some _public_ ftp server ... and
> thats really about it.  The problem with ftp is that it is not secure;
> if anyone
> is monitoring your traffic they can "listen" on all the files you send,
> and they
> can even get your password.