| File Transfer Protocol |
Article Index for File |
Shopping Protocol |
Articles about File Transfer Protocol |
Website Links For File Transfer |
Information AboutFile Transfer Protocol |
| CATEGORIES ABOUT FILE TRANSFER PROTOCOL | |
| clear text protocols | |
| network file transfer protocols | |
| ftp | |
| world wide web | |
| servers | |
| internet history | |
| application layer protocols | |
| SHOPPER'S DELIGHT | |
|
FTP or '''file transfer protocol''' is a commonly used protocol for exchanging files over any network that supports the and a Client . The '''FTP server''', running FTP server software, listens on the network for connection requests from other computers. The client computer, running FTP client software, initiates a connection to the server. Once connected, the client can do a number of file manipulation operations such as uploading files to the server, download files from the server, rename or delete files on the server and so on. Any Software company or individual programmer is able to create FTP server or client software because the protocol is an open standard. Virtually every computer platform supports the FTP protocol. This allows any computer connected to a TCP/IP based network to manipulate files on another computer on that network regardless of which Operating Systems are involved (if the computers permit FTP access). There are many existing FTP client and server programs, and many of these are free. OVERVIEW FTP is commonly run on two Ports , 20 and 21, and runs exclusively over TCP . The FTP server listens on port 21 for incoming connection from FTP clients. A connection on this port forms the control stream, on which commands are passed to the FTP server. For the actual file transfer to take place, a different connection is required. Depending on the transfer mode, the client (active mode) or the server (passive mode) can listen for the incoming data connection. Before file transfer begins, the client and server also negotiate the port of the data connection. In case of active connections (where the server connects to the client to transfer data), the server binds on port 20 before connecting to the client. For passive connections, there is no such restriction. While data is being transferred via the Data Stream , the control stream sits idle. This can cause problems with large data transfers through Firewalls which time out sessions after lengthy periods of idleness. While the file may well be successfully transferred, the control session can be disconnected by the firewall, causing an error to be generated. OBJECTIVES OF FTP The objectives of FTP, as outlined by its RFC , are: # To promote sharing of files (computer programs and/or data). # To encourage indirect or implicit use of Remote Computer s. # To shield a user from variations in file storage systems among different Host s. # To transfer Data reliably and efficiently. CRITICISMS OF FTP # Password s and file contents are sent in Clear Text , which can be intercepted by Eavesdroppers . There are protocol enhancements that circumvent this. # Multiple TCP/IP connections are used, one for the control connection, and one for each download, upload, or directory listing. Firewall software needs additional logic to account for these connections. # It is hard to filter active mode FTP traffic on the client side by using a Firewall , since the client must open an arbitrary Port in order to receive the connection. This problem is largely resolved by using passive mode FTP. # It is possible to abuse the protocol's built-in proxy features to tell a Server to send data to an arbitrary port of a third computer; see FXP . # FTP is an extremely high latency protocol due to the number of commands needed to initiate a transfer. # No integrity check on the receiver side. If transfer is interrupted the receiver has no way to know if the received file is complete or not. It is necessary to manage this externally for example with MD5 sums or Cyclic Redundancy Checking . SECURITY PROBLEMS FTP is an inherently insecure method of transferring files because there is no way for the original FTP specification to transfer data in an encrypted fashion. What this means is that under most network configurations, user names, passwords, FTP commands and transferred files can be "sniffed" or viewed by someone else on the same network using a Protocol Analyzer (or "sniffer"). It should be noted that this is a problem common to many Internet protocols written prior to the creation of SSL such as HTTP , SMTP and Telnet . The common solution to this problem is to use SFTP (SSH File Transfer Protocol) which is based on SSH , or FTPS (FTP over SSL ), which adds SSL or TLS Encryption to FTP. FTP RETURN CODES ''See also: List Of All FTP Server Return Codes .'' FTP server return codes indicate their status by the digits within them. A brief explanation of various digits' meanings are given below:
ANONYMOUS FTP Many sites that run FTP Server s enable so-called " Anonymous ftp". Under this arrangement, users do not need an Account on the server. The user name for anonymous access is typically 'anonymous' or 'ftp'. This account does not need a password. Although users are commonly asked to send their Email addresses as their passwords for authentication, usually there is trivial or no verification, depending on the FTP server and its configuration. Internet Gopher has been suggested as an alternative to anonymous FTP. DATA FORMAT While transferring data over the network, two modes can be used # ASCII mode # Binary mode The two types differ in the way they send the data. When a file is sent using an ASCII-type transfer, the individual letters, numbers and characters are sent using their ASCII character codes. The receiving machine saves these in a text file in the appropriate format (for example, a Unix machine saves it in a Unix format, a Macintosh saves it in a Mac format). Hence if an ASCII transfer is used it can be assumed Plain Text is sent, which is stored by the receiving computer in its own format. Sending a file in binary mode is different. The sending machine sends each file Bit for bit and as such the recipient stores the bitstream as it receives it. By default, most FTP clients use ASCII mode. Some clients try to determine the required transfer-mode by inspecting the file's name or contents. FTP AND WEB BROWSERS Most recent Web Browser s and File Manager s can connect to FTP servers, although they may lack the support for protocol extensions such as FTPS . This allows manipulation of remote files over FTP through an interface similar to that used for local files. This is done via an FTP URL , which takes the form ftp(s)://<''ftpserveraddress''> (e.g., {Link without Title} ). A password can optionally be given in the URL, e.g.: ftp(s)://<''login''>:<''password''>@<''ftpserveraddress''>:<''port''>. Most web-browsers require the use of passive mode FTP, which not all FTP servers are capable of handling. FTP OVER SSH The practice of tunneling a normal FTP session over an SSH connection. Since FTP (unusual for a TCP/IP protocol that is still in use) uses multiple TCP connections, it is particularly difficult to tunnel over SSH. With many SSH clients, attempting to set up a tunnel for the ''control channel'' (the initial client-to-server connection on port 21) will only protect that channel; when data is transferred, the FTP software at either end will set up new TCP connections (''data channels'') which will bypass the SSH connection, and thus have no Confidentiality , Integrity Protection , etc. If the FTP client is configured to use ''passive mode'' and to connect to a SOCKS server interface that many SSH clients can present for tunnelling, it is possible to run all the FTP channels over the SSH connection. Otherwise, it is necessary for the SSH client software to have specific knowledge of the FTP protocol, and monitor and rewrite FTP control channel messages and autonomously open new forwardings for FTP data channels. Version 3 of the SSH Communications Security Corp. software is an example of software supporting this. {Link without Title} FTP over SSH is sometimes referred to as secure FTP; this should not be confused with other methods of securing FTP, such as with SSL/TLS ( FTPS ). Other methods of transferring files using SSH which are not related to FTP include SFTP or SCP ; in both of these, the entire conversation (credentials and data) is always protected by the SSH protocol. REFERENCES The protocol is Standardized in RFC 0959 by the IETF as:
SEE ALSO FTP-like protocols
Software EXTERNAL LINKS
Tutorial/overview
|