FTP: Difference between revisions

(8 intermediate revisions by 3 users not shown)

Line 1:

'''FTP''' is an acronym for '''F'''ile '''T'''ransfer '''P'''rotocol, which is a [[TCP/IP]] based network protocol just like the [[HTTP]] used to transmit files from one computer to another through the Internet. FTP is designed to transfer small ~~multiple~~ files such as images on a web page instead of transferring a single large file. This standard protocol supports the pausing, scheduling, and restarting of file downloads.

'''FTP''' is an acronym for '''F'''ile '''T'''ransfer '''P'''rotocol, which is a [[TCP/IP]] based network protocol just like the [[HTTP]] used to transmit files from one computer to another through the Internet. FTP is designed to transfer multiple small files such as images on a web page instead of transferring a single large file. This standard protocol supports the pausing, scheduling, and restarting of file downloads.

==Objectives of FTP==

===Objectives of FTP===

Based on RFC 959, FTP has four primary objectives, which are:

Based on [[RFC]] 959, FTP has four primary objectives, which are:

# Promote file sharing (computer programs and/or data)

# Encourage indirect or implicit use of remote computers

Line 18:

==Current FTP Standard Specification==

The latest FTP standard specification implemented by the Internet Engineering Task Force ~~([[IETF~~]]) was RFC 959 which was published by Jon Postel and [[Joyce Reynolds]] on October 1985. The current RFC ~~included~~ new commands such as CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU (Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD (Print Directory) and SYST (System).<ref>[http://tools.ietf.org/html/rfc959 RFC 959]</ref>

The latest FTP standard specification implemented by the [[IETF|Internet Engineering Task Force]] was RFC 959 which was published by [[Jon Postel]] and [[Joyce Reynolds]] in October, 1985. The current RFC includes new commands such as CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU (Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD (Print Directory) and SYST (System).<ref>[http://tools.ietf.org/html/rfc959 RFC 959]</ref>

~~==FTP Commands==~~

~~===Access Control Commands===~~

* USER NAME (USER)

* PASSWORD (PASS)

* ACCOUNT (ACCT)

* CHANGE WORKING DIRECTORY (CWD)

* CHANGE TO PARENT DIRECTORY (CDUP)

* STRUCTURE MOUNT (SMNT)

* REINITIALIZE (REIN)

* LOGOUT (QUIT)

~~===Transfer Parameter Commands===~~

* DATA PORT (PORT)

* PASSIVE (PASV)

* REPRESENTATION TYPE (TYPE)

* FILE STRUCTURE (STRU)

* TRANSFER MODE (MODE)

~~===FTP Service Commands===~~

* RETRIEVE (RETR)

* STORE (STOR)

* STORE UNIQUE (STOU)

* APPEND (with create) (APPE)

* ALLOCATE (ALLO)

* RESTART (REST)

* RENAME FROM (RNFR)

* RENAME TO (RNTO)

* ABORT (ABOR)

* DELETE (DELE)

* REMOVE DIRECTORY (RMD)

* MAKE DIRECTORY (MKD)

* PRINT WORKING DIRECTORY (PWD)

* LIST (LIST)

* NAME LIST (NLST)

* SITE PARAMETERS (SITE)

* SYSTEM (SYST)

* HELP (HELP)

* NOOP (NOOP)

==Anonymous FTP==

Line 63:

Line 24:

==Security Issues==

Although the FTP was designed to transfer data efficiently and reliably, the protocol has security loopholes because data ~~are~~ transmitted ~~on a~~ plain text and it ~~does~~ have any provision for data encryption. Hackers can easily steal users passwords, read and monitor private files and conversations and they can also install viruses.<ref>[http://www.ncftp.com/libncftp/doc/ftp_overview.html An Overview of the File Transfer Protocol; Security Concerns]</ref> Mark Allman from NASA Glenn Research Center/Sterling Software and Shawn Ostermann from Ohio University School of Electrical Engineering and Computer Science wrote RFC 2577 and identified three security problems associated with FTP such as '''Bounce Attacks''', '''Spoof attacks''' and '''Denial of Service Attacks''' and suggested measures to reduce or prevent security problems associated with FTP.<ref>[http://tools.ietf.org/html/rfc2577 RFC 2577]</ref>

Although the FTP was designed to transfer data efficiently and reliably, the protocol has security loopholes because data is transmitted in plain text and it doesn't have any provision for data encryption. Hackers can easily steal users passwords, read and monitor private files and conversations, and they can also install viruses.<ref>[http://www.ncftp.com/libncftp/doc/ftp_overview.html An Overview of the File Transfer Protocol; Security Concerns]</ref> Mark Allman from NASA Glenn Research Center/Sterling Software and Shawn Ostermann from Ohio University School of Electrical Engineering and Computer Science wrote RFC 2577 and identified three security problems associated with FTP such as '''Bounce Attacks''', '''Spoof attacks''' and '''Denial of Service Attacks''' and suggested measures to reduce or prevent security problems associated with FTP.<ref>[http://tools.ietf.org/html/rfc2577 RFC 2577]</ref>

==References==

== References ==

~~__NOTOC__~~

[[Category: Glossary]]

@@ Line 1: / Line 1: @@
-'''FTP''' is an acronym for  '''F'''ile '''T'''ransfer '''P'''rotocol, which is a [[TCP/IP]] based network protocol just like the [[HTTP]] used to transmit files from one computer to another through the Internet. FTP is designed to transfer small multiple files such as images on a web page instead of transferring a single large file. This standard protocol supports the pausing, scheduling, and restarting of file downloads.
+'''FTP''' is an acronym for  '''F'''ile '''T'''ransfer '''P'''rotocol, which is a [[TCP/IP]] based network protocol just like the [[HTTP]] used to transmit files from one computer to another through the Internet. FTP is designed to transfer multiple small files such as images on a web page instead of transferring a single large file. This standard protocol supports the pausing, scheduling, and restarting of file downloads.
-==Objectives of FTP==
+===Objectives of FTP===
-Based on RFC 959, FTP has four primary objectives, which are:
+Based on [[RFC]] 959, FTP has four primary objectives, which are:
 # Promote file sharing (computer programs and/or data)
 # Encourage indirect or implicit use of remote computers
@@ Line 18: / Line 18: @@
 ==Current FTP Standard Specification==
-The latest FTP standard specification implemented by the Internet Engineering Task Force ([[IETF]]) was  RFC 959 which was published by Jon Postel and [[Joyce Reynolds]] on October 1985. The current RFC included new commands such as CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU (Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD (Print Directory) and SYST (System).<ref>[http://tools.ietf.org/html/rfc959 RFC 959]</ref>
+The latest FTP standard specification implemented by the [[IETF|Internet Engineering Task Force]] was  RFC 959 which was published by [[Jon Postel]] and [[Joyce Reynolds]] in October, 1985. The current RFC includes new commands such as CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU (Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD (Print Directory) and SYST (System).<ref>[http://tools.ietf.org/html/rfc959 RFC 959]</ref>
-==FTP Commands==
-===Access Control Commands===
-* USER NAME (USER)
-* PASSWORD (PASS)
-* ACCOUNT (ACCT)
-* CHANGE WORKING DIRECTORY (CWD)
-* CHANGE TO PARENT DIRECTORY (CDUP)
-* STRUCTURE MOUNT (SMNT)
-* REINITIALIZE (REIN)
-* LOGOUT (QUIT)
-===Transfer Parameter Commands===
-* DATA PORT (PORT)
-* PASSIVE (PASV)
-* REPRESENTATION TYPE (TYPE)
-* FILE STRUCTURE (STRU)
-* TRANSFER MODE (MODE)
-===FTP Service Commands===
-* RETRIEVE (RETR)
-* STORE (STOR)
-* STORE UNIQUE (STOU)
-* APPEND (with create) (APPE)
-* ALLOCATE (ALLO)
-* RESTART (REST)
-* RENAME FROM (RNFR)
-* RENAME TO (RNTO)
-* ABORT (ABOR)
-* DELETE (DELE)
-* REMOVE DIRECTORY (RMD)
-* MAKE DIRECTORY (MKD)
-* PRINT WORKING DIRECTORY (PWD)
-* LIST (LIST)
-* NAME LIST (NLST)
-* SITE PARAMETERS (SITE)
-* SYSTEM (SYST)
-* HELP (HELP)
-* NOOP (NOOP)
 ==Anonymous FTP==
@@ Line 63: / Line 24: @@
 ==Security Issues==
-Although the FTP was designed to transfer data efficiently and reliably, the protocol has security loopholes because data are transmitted on a plain text and it does have any provision for data encryption. Hackers can easily steal users passwords, read and monitor private files and conversations and they can also install viruses.<ref>[http://www.ncftp.com/libncftp/doc/ftp_overview.html An Overview of the File Transfer Protocol; Security Concerns]</ref> Mark Allman from NASA Glenn Research Center/Sterling Software and Shawn Ostermann from Ohio University School of Electrical Engineering and Computer Science wrote RFC 2577 and identified three security problems associated with FTP such as '''Bounce Attacks''', '''Spoof attacks'''  and  '''Denial of Service Attacks''' and suggested measures to reduce or prevent security problems associated with FTP.<ref>[http://tools.ietf.org/html/rfc2577 RFC 2577]</ref>
+Although the FTP was designed to transfer data efficiently and reliably, the protocol has security loopholes because data is transmitted in plain text and it doesn't have any provision for data encryption. Hackers can easily steal users passwords, read and monitor private files and conversations, and they can also install viruses.<ref>[http://www.ncftp.com/libncftp/doc/ftp_overview.html An Overview of the File Transfer Protocol; Security Concerns]</ref> Mark Allman from NASA Glenn Research Center/Sterling Software and Shawn Ostermann from Ohio University School of Electrical Engineering and Computer Science wrote RFC 2577 and identified three security problems associated with FTP such as '''Bounce Attacks''', '''Spoof attacks'''  and  '''Denial of Service Attacks''' and suggested measures to reduce or prevent security problems associated with FTP.<ref>[http://tools.ietf.org/html/rfc2577 RFC 2577]</ref>
-==References==
+== References ==
 {{reflist}}
-__NOTOC__
 [[Category: Glossary]]