Follow Us On

Large Files on twitter Airdrie political opinion on youtube Follow Large File Transfer on delicious Large EMail on Technorati

Subscribe via E-mail

Your email:

Large File Transfer Blog

Current Articles |  RSS Feed

Secure File Sharing Methods

  | Share on Twitter Twitter | Share on Facebook Facebook |   Google Buzz |  digg it |   delicious |   StumbleUpon |  Share on LinkedIn LinkedIn |   Technorati |  reddit | 

For thirty years, FTP has been the default method of moving files around networks, including the internet.  It's no surprise that FilesDIRECT replaces FTP, but on what basis?

The real question is: on what basis does it not?

Security - For the past thirty years, plain FTP has ignored security concerns, passing its passwords across the net in plain text.  In today's world that's completely unacceptable, especially with the huge rise in easily eaves-droppable mobile devices.  Also, FTP plays havoc with firewalls, opening a new connection for every file, which makes your network less secure (especially when the firewall is configured out of desperation to allow FTP, but disallow better security.)  FilesDIRECT is SSL-encrypted every time, and nothing passes in plain text.

(Photo: Dazzie D)

Usability - Timestamps on files aren't kept with FTP, leaving users lost as to what version of what file they're looking at after a transfer. Directory listings aren't standardized, meaning users can be stuck working with clumsy, incorrect information about what files are where.  FilesDIRECT uses easy to read links and lists to display directories and timestamps are what they're supposed to be.

Simplicity - FTP clients are confusing, especially for new users. What thirty year old software technology wouldn't be? By comparison, if you can use email and a web browser, you can use FilesDIRECT.

Sadly, FTP won't be going away any time soon. The good news is you don't have to keep using it: now you can choose FilesDIRECT!

Comments

Currently, there are no comments. Be the first to post one!
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics