The three most common ways of using FTP include:
- Via a web browser: With a web browser, you do not need any special software or a client to download files from servers that provide for FTP sites.
- A general user interface (GUI) FTP client: These third-party applications enable users to connect and then send files over FTP.
- Command-line FTP: Major operating systems come equipped with FTP client capabilities as a command line.
An FTP port is a communication endpoint and allows data transfer between a computer and a server. A computer’s operating system only uses a specific number of ports, which are necessary for software to connect through a network. An FTP port is required for the client and server to quickly exchange files.
FTP stands for File Transfer Protocol, while SFTP refers to Secure Shell (SSH) File Transfer Protocol. This gives you file transfers that are secured via SSH, which provides full access to shell accounts. A shell account is one that sits on a remote server.
FTP is different from SFTP in that it does not give users a secure channel for transferring files. Also, FTP makes use of two channels for transferring data, but SFTP only uses a single channel. The inbound connections that each protocol uses are different as well. FTP defaults to port 21, but SFTP allows inbound communication on port 22.
The manner in which data is transferred is also significantly different. SFTP uses a tunneling method to transfer data. With the benefit of additional security, FTP, which is less secure, uses direct transfer.
Even though Hyper Text Transfer Protocol (HTTP) and FTP are similar in that they are application-layer protocols that enable you to send files between systems, there are some key differences. HTTP can support multiple sessions at the same time because it is a stateless protocol. This means it does not save the data used in a session to employ it in the next one.
FTP, on the other hand, is stateful, which means it collects data about the client and uses it in the next request the client makes. Because FTP performs this function, it is limited in the number of sessions it can support simultaneously. Regardless of the bandwidth of a network, HTTP has the potential to be a much more efficient method of data transmission.
Another key difference is that with FTP, there needs to be client authentication before information is transferred. With HTTP, no client authentication is needed. HTTP uses a well-known, common port, making it easy for firewalls to work with. In some cases, FTP can be more difficult for a firewall to manage.
In some ways, managed file transfer (MFT) is the new kid on the block when compared to FTP. FTP, while effective in many settings, was not designed to accommodate the complex threat landscape people are forced to deal with today. In fact, there has even been an official warning issued by the FBI regarding the potential pitfalls of using FTP—even that which is secured with SSL and SSH.
As the name suggests, managed file transfer comes with management and various compliance and security features. It is important for these to be in place, not just to make data transfer safer but to appease the authorities that require secure data transfer, particularly in companies that handle sensitive data such as patient medical records. Normal FTP leaves data transfers open to an eavesdropping attack or a banker Trojan, which targets financial institutions.
Even though you could manually program the security and management features necessary for safer FTP transmissions, MFT saves you the time and energy. If, for example, two people were using the Mist Browser to configure dapps on Ethereum, a hacker could intercept their communications before they reached the FTP port. The hacker could then sell what was intercepted to a competitor, who could use it to make a similar dapp and release it sooner, thus gaining a strategic advantage.
Application servers are assigned default port numbers, but if you want to change them, there are two ways you can do so:
- Go to your FTP application’s settings page, and change the port number from there.
- Add the port number to the FTP server address. To do this, add a colon plus the new port number to the end of the FTP server address—before “/” if there is one. For example: ftp:/mydomain.com:####/—where each “#” is a digit.