![FTP is built on a client-server architecture and uses separate control and
data connections between the client and the server.[1] FTP users may
authenticate themselves using aclear-text sign-in protocol, normally in
the form of a username and password, but can connect anonymously if
the server is configured to allow it. For secure transmission that protects
the username and password, and encrypts the content, FTP is
often secured with SSL/TLS (FTPS). SSH File Transfer Protocol (SFTP)
is sometimes also used instead, but is technologically different.
The first FTP client applications were command-line
applications developed before operating systems had graphical user
interfaces, and are still shipped with most Windows, Unix,
and Linux operating systems.[2][3] Many FTP clients and automation
utilities have since been developed for desktops, servers, mobile
devices, and hardware, and FTP has been incorporated into productivity
applications, such as Web page editors.](https://image.slidesharecdn.com/laxmijindal-ix-d-141015023350-conversion-gate02/85/FILE-TRANSFER-PROTOCOL-BY-LAXMI-Group-6-320.jpg)
![FTP may run in active or passive mode, which
determines how the data connection is
established.[5] In both cases, the client creates a TCP
control connection from a random unprivileged port
N to the FTP server command port 21. In active
modes, the client starts listening for incoming data
connections on port N+1 from the server (the client
sends the FTP command PORT N+1 to inform the
server on which port it is listening). In situations
where the client is behind a firewall and unable to
accept incoming TCP connections, passive
mode may be used. In this mode, the client uses the
control connection to send a PASV command to the
server and then receives a server IP address and
server port number from the server,[5][6] which the
client then uses to open a data connection from an
arbitrary client port to the server IP address and
server port number received.](https://image.slidesharecdn.com/laxmijindal-ix-d-141015023350-conversion-gate02/85/FILE-TRANSFER-PROTOCOL-BY-LAXMI-Group-11-320.jpg)
![Stream mode: Data is sent as a continuous stream,
relieving FTP from doing any processing. Rather, all
processing is left up to TCP. No End-of-file indicator is
needed, unless the data is divided into records.
Block mode: FTP breaks the data into several blocks
(block header, byte count, and data field) and then
passes it on to TCP.[4]
Compressed mode: Data is compressed using a single
algorithm (usually run-length encoding).](https://image.slidesharecdn.com/laxmijindal-ix-d-141015023350-conversion-gate02/85/FILE-TRANSFER-PROTOCOL-BY-LAXMI-Group-12-320.jpg)
FILE TRANSFER PROTOCOL BY LAXMI $ Group
- 3. 1.What is FTP ? 2.History of FTP 3.Types of FTP 4.Transferring Data 5.Login 6.Security 7.Logo 8.Bibliography 9.Acknowledgement
- 6. FTP is built on a client-server architecture and uses separate control and data connections between the client and the server.[1] FTP users may authenticate themselves using aclear-text sign-in protocol, normally in the form of a username and password, but can connect anonymously if the server is configured to allow it. For secure transmission that protects the username and password, and encrypts the content, FTP is often secured with SSL/TLS (FTPS). SSH File Transfer Protocol (SFTP) is sometimes also used instead, but is technologically different. The first FTP client applications were command-line applications developed before operating systems had graphical user interfaces, and are still shipped with most Windows, Unix, and Linux operating systems.[2][3] Many FTP clients and automation utilities have since been developed for desktops, servers, mobile devices, and hardware, and FTP has been incorporated into productivity applications, such as Web page editors.
- 7. The original specification for the File Transfer Protocol was written by Abhay Bhushan and published as RFC 114 on 16 April 1971. Until 1980, FTP ran on NCP, the predecessor of TCP/IP. The protocol was later replaced by a TCP/IP version, RFC 765 (June 1980) and RFC 959 (October 1985), the current specification. Several proposed standards amend RFC 959, for example RFC 2228 (June 1997) proposes security extensions and RFC 2428 (September 1998) adds support for IPv6 and defines a new type of passive mode.
- 9. There are 2 types of file transfers: Pull-based file transfers where the receiver initiates a file transmission request. Push-based file transfers where the sender initiates a file transmission request. File transfer can take place over a variety of levels: Transparent file transfers over network file systems. Explicit file transfers from dedicated file transfer services like FTP or HTTP Distributed file transfers over peer-to-peer networks like Bittorent or Gnutella
- 11. FTP may run in active or passive mode, which determines how the data connection is established.[5] In both cases, the client creates a TCP control connection from a random unprivileged port N to the FTP server command port 21. In active modes, the client starts listening for incoming data connections on port N+1 from the server (the client sends the FTP command PORT N+1 to inform the server on which port it is listening). In situations where the client is behind a firewall and unable to accept incoming TCP connections, passive mode may be used. In this mode, the client uses the control connection to send a PASV command to the server and then receives a server IP address and server port number from the server,[5][6] which the client then uses to open a data connection from an arbitrary client port to the server IP address and server port number received.
- 12. Stream mode: Data is sent as a continuous stream, relieving FTP from doing any processing. Rather, all processing is left up to TCP. No End-of-file indicator is needed, unless the data is divided into records. Block mode: FTP breaks the data into several blocks (block header, byte count, and data field) and then passes it on to TCP.[4] Compressed mode: Data is compressed using a single algorithm (usually run-length encoding).
- 18. Wikipedia Images