Originally posted by: kamper
Originally posted by: Lord Evermore
You're aware that pretty much every web browser supports FTP right in the browser window, giving you a simple directory listing for all the files and folders? And this person is the one hosting the server, his friends are going to be downloading, so by your reasoning FTP is perfectly acceptable because they could just do anonymous downloading.
Sure, ftp is fine for anonymous downloading from a security perspective (just the extra ports are a bit of a hassle). I was reacting to the completely incorrect statement that "ftp is only the protocol made for file transfer" and I was assuming we were talking about traffic in both directions by that point.
For the vast majority of people, having to set up full FTP/SFTP/SSH access and server software is beyond their capabilities. If somebody really wants sftp on a Windows box, they can get the software themselves. MS already charges enough for Windows, don't give them an excuse to up the price by adding in (another) something hardly anybody needs.
All I'd really care about is client support and that couldn't possibly take that much time given that there are free implementations out there to be had. Server support would be nice with the server and pro versions, after all, IIS includes ftp and smtp.
Simple free FTP server software is nearly plug and play, all you have to do is point it to the folder to use and create an account for people, or allow anonymous login.
And why couldn't there be simple free sftp software? It'd be even more simple than ftp because you wouldn't have to fuss with extra ports and passive vs. non-passive connections. I guess there's the extra hassle of seeing messages about unknown certs but at the very least, you're no less secure than with ftp then.
Actually my sftp server is even easier than most ftp servers. I just answer 'y' during the os install when it asks me if I want ssh enabled

It doesn't need to be complicated.
Who cares if somebody could, in the vastness of the Internet, intercept the login name and password which you're only using for this one application for a short period, and can easily change, and which they probably couldn't do any damage with?
You're right of course, within the scope of what the op was asking. Again, I was just referring to the protocol issue in general, as previously mentioned. Sftp ought to be as simple as ftp and at that point I don't think there's any conceivable reason to continue to use ftp.
Do you send your email encrypted?
No, and of course that's not ideal but it's a slightly harder problem to fix when you don't control all the servers in between. That's not a valid excuse to keep on using ftp though.