FTP v/s SFTP v/s FTPS
Solution 1:
So the two sane options these days are:
WebDAV, nice on the server side, nice for Linux and Mac OS clients, however the inbuilt Windows client has issues.
SCP/SFTP, very easy as you're likely to have ssh anyway, GUI clients easily available (FileZilla for example)
Although FTP is still around I'd really avoid setting anything new up based on it.
Solution 2:
I think the short answer is to use an FTP server that supports all three protocols. You probably want to avoid allowing FTP since you mentioned security as a primary concern but both the SSH2 File Transfer Protocol (SFTP) and FTP over TLS/SSL (FTPS) are considered secure file transfer protocols.
SFTP is definitely the favorite these days because of its robust security model and easier setup than traditional FTP and FTPS. SFTP is also considerably more firewall friendly than FTP because it only requires one port to establish a connection and carry out file operations.
FTP and FTPS require multiple ports (one port to issue commands and a separate port for each and every directory listing or file transfer) to accomplish the same thing that SFTP can do with one port. The requirement to setup forwarding for large numbers of ports can be a problem in many environments and can make troubleshooting problems very difficult. However, FTP and FTPS have been around a lot longer than SFTP and there are still lots of devices and clients that only support FTPS.
In terms of security, both the SFTP and FTPS protocols are considered secure. The requirement to open up multiple ports with FTPS can be viewed as a security concern but there is nothing inherently more secure about the SFTP protocol over the FTPS protocol.
The only real advantage I would give FTPS over SFTP would be performance. SFTP runs over a considerably more robust and generic protocol than FTPS and that robustness imparts a significant performance impact. There is simply a lot more overhead involved in SFTP because it is running over the SSH2 protocol and because SFTP implements its own handshaking mechanism. If you want the highest transfer speeds possible you want FTPS.
To sum all of this up, try to support all 3. Most modern FTP servers already have support for FTP, FTPS, and SFTP.
Solution 3:
Any-one interested in some numbers here are my results from running some benchmarks on my local network. SMB 2.1 performance is about 112 MB/s
Machine: Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz/8GB ram/Gigabit Local Network
FTP Mode MB/s CPU Usage/APP Encrypted
-------------------------------------------------------------
FTP Transfer rate: 120 40.9 proftpd No
FTPS (SSL) Transfer Rate: 55 99.8% proftpd Yes
SFTP Transfer Rate: 30 100% sshd Yes
Putty SSH Tunnel, (Raw) FTP: 32 100% sshd Yes
Solution 4:
Definitely avoid installing an FTP daemon. As long as you have SSH, you have SFTP. No extra set up required. The only reason to use FTP is for the masses.
I run an FTP server that also supports FTPES (FTP over explicit SSL) and I really see no advantages of it, aside from the fact that it is already in place. I inherited it, and all the user accounts and permissions work. But for everything else, I just use SSH/SFTP.