On Wednesday 28 February 2007, Joaquin Herrero wrote: > I checked this product and it's really impressive. I will definitely try it > but not for this project. I have to setup a secure FTP because the > transfers are really big: hundreds of scans per day. > > People involved in this project are used to make bulk transfers in the > background using "programmable" FTP clients, so for this project what I > need is a robust and secure FTP. I used until now a Windows machine with a > third party FTP server, but now I have to open this service to users in the > Internet, so Windows is not an option in this new scenario. The options are > Linux or OpenBSD, and I would like to use OpenBSD of course.
Maybe both Linux and openBSD. Use Linux as an ftp server so that cifs is available for mounting the remote filesystem (smbfs would be useless anyway do to its 2GB limit and other issues - it's deprcated). Since the files are huge, a non-encrypted data stream (ftp vs. sftp) will be much faster. If some paranoia exists with ftp's use of non-encrypted password, place an openBSD box running authpf on the frontend (if you already have an openBSD firewall no need for a new box) allowing ftp access on authentication. Chris
