RFC 2577: FTP Security Considerations
In plain English — editorial summary, not part of the RFC
This document provides suggestions for system administrators and those implementing FTP servers that will decrease the security problems associated with FTP. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2577
- Published
- May 1999
- Authors
- M. Allman; S. Ostermann
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2415Simulation Studies of Increased Initial TCP Window SizeCurrent
September 1998
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 1635How to Use Anonymous FTPCurrent
May 1994
- RFC 2518HTTP Extensions for Distributed Authoring -- WEBDAVObsoleted
February 1999
- RFC 2696LDAP Control Extension for Simple Paged Results ManipulationCurrent
September 1999
- RFC 2310The Safe Response Header FieldCurrent
April 1998
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 2936HTTP MIME Type Handler DetectionCurrent
September 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?