If not FTP, then what?

Often times I get told that I should not use a FTP program to transfer files from and to a server.
My question is, if I can’t use FTP to transfer the files, what AM I supposed to use?

See, anytime you are online, your computer is open and you are exposed to risks. It then boils down to which one is least risky :). Search on google for “java security issues”, you wont find any, then search for “ftp security issues” and you will see that FTP is way insecure.

From my understanding, Binfer does not connect to any file sharing network such as torrent. I did a quick wireshark test and didnt see any conenctions to random PC’s. It creates a direct VPN type connection between two end points, and xfers with 128bit AES encryption, which imho is more secure than running a FTP server. With FTP you have open a port on your firewall, secure it, manage users etc.

FTP was created in the yesteryears because the model was client server. These days with high speed networks and powerful computers, this new solution works well, at least for me. I guess it will take time to change the mindset from client server to direct p2p.

Most of the freeware ftp programs also support SFTP now. Try the one which you like the most. But again, first make sure that your host supports this feature.

I really dont see that as being a viable alternative to FTP/SFTP. I dont feel overly comfortable opening my computer up to a Java application that connects to a file sharing network. Call me Mr Paranoid if you like but thats just my opinion.

cant you use a regular FTP client for SFTP… it is just using the security feature and a different login?

You need a client on your machine like SecureCRT from VanDyke Software (or VShell, or SecureFX, etc) that will allow you to make the secure connection to the remote server for file transfer. But I suppose an alternative to FTP would be a managed file transfer service, such as MFT from axway.com or using a web server with SSL where you upload files through a web form submission.

On the Microsoft side here are a few options . . .

FTPS
Use FTP over SSL (FTPS) functionality of the FTP7 server from Internet Information Server and Windows Server 2008.

WebDAV
Use the WebDAV extensions to Windows Server 2008 to enable document exchange in Internet Information Server. WebDAV enables file manipulation through a web interface, secured using HTTP over SSL (HTTPS).

Sharepoint
Use document libraries in Sharepoint Services or Sharepoint Server. This allows you to share files in a web interface, secured using HTTP over SSL (HTTPS). Take a look at Sharepoint Services 3.0 and Microsoft Office Sharepoint Server 2007 if you want the ability to access a document library as a file share (no need to upload files in a web interface). You could share these files using FTP over SSL functionality described above for people who want to continue using FTP style communication.

Exchange Public Folders
Use Microsoft Exchange Server with Public Folders.

I think you have a lot of FTP alternatives. The main idea is to encrypt the file transfer connection between yourself (client) and the website (server).

FTP is becoming a thing of the past. Direct file transfer [DFT] is the new thing… the way file transfers were was intended to be in the first place [TCP/IP spec]. I use Binfer instead of FTP for data transfer. If you are interested check it out here: http://www.binfer.com. I run it on my XP box at home and on the CentOS[Gnome] on Godaddy and xfer files. Dont have to open ports etc. Love it.

I never expected SFTP to just be a matter of switching the server type option in my ftp client…can’t be easier. :stuck_out_tongue:
Obviously I had ssh enabled beforehand.

Most regular FTP clients do support SFTP, I use SmartFTP myself and they’ve had support for years, but not all products do so you’ll need to check. :slight_smile:

Yes, SFTP is the best replacement for FTP over all. There’s also FTPS.

Perhaps they want you to use SFTP instead.

Yea, many people now prefer to use SFTP over SSH because it effectively forms an encrypted connection between you and the server (so information can’t be intercepted between). Most FTP clients support sFTP so it shouldn’t be that much of an issue to make the switch, just make sure that your host actually supports the protocol (else you’ll be out of luck!). I personally use SmartFTP as my FTP client and I’ve been using SFTP over SSH for ages. :slight_smile: