As a former host and someone who manages both a semi-public linux server as well as Windows servers at work, let me ask a question. How does an enterprise claim security in their systems when they allow their users to use FTP to transfer files? The tried and true method of moving files to the internet for use on the web is File Transfer Protocol. Well, it’s tried anyways. The fact is that FTP broadcasts username and password in plaintext. People are getting sold a bill of goods if they believe they can’t get hacked, their sites can’t be exploited, they are on a “secure” web server when FTP is running. The same can be said of Telnet but thankfully, telnet is generally disabled.
So what to do about FTP? The answer? SFTP, or Secure File Transfer Protocol. Not a new technology. Just more unknown and uncommon. It is FTP over Secure Shell protocol. The same way users would login to the commandline of their linux web hosting is the same protocol that SFTP works on.
Next time you work on a website, try SFTP instead of FTP. You’ll find that your site is less likely to be hacked.
Cheers.
Aaron




Viewing 5 Comments
Thanks. Your comment is awaiting approval by a moderator.
Do you already have an account? Log in and claim this comment.
Do you already have an account? Log in and claim this comment.
=&instead of=when assigning those data variables (title, artist, album, etc..)Do you already have an account? Log in and claim this comment.
Do you already have an account? Log in and claim this comment.
I am still torn between creativity and Section 508, but I have found that following simple coding standards eliminates many accessibility issues.
Do you already have an account? Log in and claim this comment.
Anyway, SFTP isn't really FTP. It's really just a wrapper around scp. But nice recommedation. I often don't run a FTP daemon by default.
Do you already have an account? Log in and claim this comment.