Changes

Jump to navigation Jump to search
no edit summary
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)
 
# Promote file sharing (computer programs and/or data)
 
# Encourage indirect or implicit use of remote computers
 
# Encourage indirect or implicit use of remote computers
Line 24: Line 24:     
==Security Issues==
 
==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==

Navigation menu