BSD 4_1c_2 development

Work on file usr/man/man8/ftpd.8

Synthesized-from: CSRG/cd1/4.1c.2

diff --git a/usr/man/man8/ftpd.8 b/usr/man/man8/ftpd.8
new file mode 100644 (file)
index 0000000..f76f13a
--- /dev/null
+++ b/usr/man/man8/ftpd.8
@@ -0,0 +1,134 @@
+.TH FTPD 8C "4 March 1983"
+.UC 4
+.SH NAME
+ftpd \- DARPA Internet File Transfer Protocol server
+.SH SYNOPSIS
+.B /etc/ftpd
+[
+.B \-d
+]
+.SH DESCRIPTION
+.I Ftpd
+is the DARPA Internet File Transfer Prototocol
+server process.  The server uses the TCP protocol
+and listens at the port specified in the ``ftp''
+service specification; see
+.IR services (5).
+.PP
+If the 
+.B \-d
+option is specified when the server is started up,
+each socket created will have debugging turned
+on (SO_DEBUG).  With debugging enabled, the system
+will trace all TCP packets sent and received on a
+socket.  The program
+.IR trpt (8C)
+may then be used to interpret the packet traces.
+.PP
+The ftp server currently supports the following ftp
+requests;  case is not distinguished.
+.PP
+.nf
+.ta \w'Request        'u
+\fBRequest     Description\fP
+ACCT   specify account (ignored)
+ALLO   allocate storage (vacuously)
+APPE   append to a file
+CWD    change working directory
+DELE   delete a file
+HELP   give help information
+LIST   give list files in a directory (``ls -lg'')
+MODE   specify data transfer \fImode\fP
+NLST   give name list of files in directory (``ls'')
+NOOP   do nothing
+PASS   specify password
+PORT   specify data connection port
+QUIT   terminate session
+RETR   retrieve a file
+RNFR   specify rename-from file name
+RNTO   specify rename-to file name
+STOR   store a file
+STRU   specify data transfer \fIstructure\fP
+TYPE   specify data transfer \fItype\fP
+USER   specify user name
+XCUP   change to parent of current working directory
+XCWD   change working directory
+XMKD   make a directory
+XPWD   print the current working directory
+XRMD   remove a directory
+.fi
+.PP
+The remaining ftp requests specified in Internet RFC 765 are
+recognized, but not implemented.
+.PP
+.I Ftpd
+interprets file names according to the ``globbing''
+conventions used by
+.IR csh (1).
+This allows users to utilize the metacharacters ``*?[]{}~''.
+.PP
+.I Ftpd
+authenticates users according to three rules. 
+.IP 1)
+The user name must be in the password data base,
+.IR /etc/passwd ,
+and not have a null password.  In this case a password
+must be provided by the client before any file operations
+may be performed.
+.IP 2)
+The user name must not appear in the file
+.IR /etc/ftpusers .
+.IP 3)
+If the user name is ``anonymous'' or ``ftp'', an
+anonymous ftp account must be present in the password
+file (user ``ftp'').  In this case the user is allowed
+to log in by specifying any password (by convention this
+is given as the client host's name).
+.PP
+In the last case, 
+.I ftpd
+takes special measures to restrict the client's access privileges.
+The server performs a 
+.IR chroot (2)
+command to the home directory of the ``ftp'' user and interprets
+path names to insure references are maintained within the subtree.
+In order that system security is not breached, it is recommended
+that the ``ftp'' subtree be constructed with care;  the following
+rules are recommended.
+.IP ~ftp)
+Make the home directory owned by ``ftp'' and unwritable by anyone.
+.IP ~ftp/bin)
+Make this directory owned by the super-user and unwritable by
+anyone.  The programs
+.IR sh (1)
+and
+.IR ls (1)
+must be present to support the list commands.  These
+programs should have mode 111.
+.IP ~ftp/etc)
+Make this directory owned by the super-user and unwritable by
+anyone.  The files
+.IR passwd (5)
+and
+.IR group (5)
+must be present for the 
+.I ls
+command to work properly.  These files should be mode 444.
+.IP ~ftp/pub)
+Make this directory mode 777 and owned by ``ftp''.  Users
+should then place files which are to be accessible via the
+anonymous account in this directory.
+.SH "SEE ALSO"
+ftp(1C),
+.SH BUGS
+There is no support for aborting commands.
+.PP
+The anonymous account is inherently dangerous and should
+avoided when possible.
+.PP
+The server must run with real user id of the super-user
+to create sockets with privileged port numbers.  It maintains
+an effective user id of the logged in user, reverting to
+the super-user only when binding addresses to sockets.  The
+possible security holes have been extensively
+scrutinized, but are possibly incomplete.