1.\" Copyright (c) 1985, 1988, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the following acknowledgement: 14.\" This product includes software developed by the University of 15.\" California, Berkeley and its contributors. 16.\" 4. Neither the name of the University nor the names of its contributors 17.\" may be used to endorse or promote products derived from this software 18.\" without specific prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)ftpd.8 8.2 (Berkeley) 4/19/94 33.\" $FreeBSD$ 34.\" 35.Dd January 27, 2000 36.Dt FTPD 8 37.Os 38.Sh NAME 39.Nm ftpd 40.Nd Internet File Transfer Protocol server 41.Sh SYNOPSIS 42.Nm 43.Op Fl 46AdDEmMoOrRSUvW 44.Op Fl l Op Fl l 45.Op Fl a Ar address 46.Op Fl p Ar file 47.Op Fl t Ar timeout 48.Op Fl T Ar maxtimeout 49.Op Fl u Ar umask 50.Sh DESCRIPTION 51The 52.Nm 53utility is the 54Internet File Transfer Protocol 55server process. The server uses the 56.Tn TCP 57protocol 58and listens at the port specified in the 59.Dq ftp 60service specification; see 61.Xr services 5 . 62.Pp 63Available options: 64.Bl -tag -width indent 65.It Fl 4 66When 67.Fl D 68is specified, accept IPv4 connections. 69When 70.Fl 6 71is also specified, accept IPv4 connection via 72.Dv AF_INET6 73socket. 74When 75.Fl 6 76is not specified, accept IPv4 connection via 77.Dv AF_INET 78socket. 79.It Fl 6 80When 81.Fl D 82is specified, accept connections via 83.Dv AF_INET6 84socket. 85.It Fl a 86When 87.Fl D 88is specified, accept connections only on the specified 89.Ar address . 90.It Fl A 91Allow only anonymous ftp access. 92.It Fl d 93Debugging information is written to the syslog using 94.Dv LOG_FTP . 95.It Fl D 96With this option set, 97.Nm 98will detach and become a daemon, accepting connections on the FTP port and 99forking children processes to handle them. 100This is lower overhead than starting 101.Nm 102from 103.Xr inetd 8 104and is thus useful on busy servers to reduce load. 105.It Fl E 106Disable the EPSV command. 107This is useful for servers behind older firewalls. 108.It Fl l 109Each successful and failed 110.Xr ftp 1 111session is logged using syslog with a facility of 112.Dv LOG_FTP . 113If this option is specified twice, the retrieve (get), store (put), append, 114delete, make directory, remove directory and rename operations and 115their filename arguments are also logged. 116Note: 117.Dv LOG_FTP 118messages 119are not displayed by 120.Xr syslogd 8 121by default, and may have to be enabled in 122.Xr syslogd 8 Ns 's 123configuration file. 124.It Fl m 125Permit anonymous users to overwrite or modify 126existing files if allowed by filesystem permissions. 127By default, anonymous users cannot modify existing files; 128in particular, files to upload will be created under a unique name. 129.It Fl M 130Prevent anonymous users from creating directories. 131.It Fl o 132Put server in write-only mode. 133RETR is disabled, preventing downloads. 134.It Fl O 135Put server in write-only mode for anonymous users only. 136RETR is disabled for anonymous users, preventing anonymous downloads. 137This has no effect if 138.Fl o 139is also specified. 140.It Fl p 141When 142.Fl D 143is specified, write the daemon's process ID to 144.Ar file . 145.It Fl r 146Put server in read-only mode. 147All commands which may modify the local filesystem are disabled. 148.It Fl R 149With this option set, 150.Nm 151will revert to historical behavior with regard to security checks on 152user operations and restrictions on PORT requests. 153Currently, 154.Nm 155will only honor PORT commands directed to unprivileged ports on the 156remote user's host (which violates the FTP protocol specification but 157closes some security holes). 158.It Fl S 159With this option set, 160.Nm 161logs all anonymous file downloads to the file 162.Pa /var/log/ftpd 163when this file exists. 164.It Fl t 165The inactivity timeout period is set to 166.Ar timeout 167seconds (the default is 15 minutes). 168.It Fl T 169A client may also request a different timeout period; 170the maximum period allowed may be set to 171.Ar timeout 172seconds with the 173.Fl T 174option. 175The default limit is 2 hours. 176.It Fl u 177The default file creation mode mask is set to 178.Ar umask , 179which is expected to be an octal numeric value. 180Refer to 181.Xr umask 2 182for details. 183.It Fl U 184In previous versions of 185.Nm , 186when a passive mode client requested a data connection to the server, 187the server would use data ports in the range 1024..4999. Now, by default, 188the server will use data ports in the range 49152..65535. Specifying this 189option will revert to the old behavior. 190.It Fl v 191A synonym for 192.Fl d . 193.It Fl W 194Don't log FTP sessions to 195.Pa /var/log/wtmp . 196.El 197.Pp 198The file 199.Pa /var/run/nologin 200can be used to disable ftp access. 201If the file exists, 202.Nm 203displays it and exits. 204If the file 205.Pa /etc/ftpwelcome 206exists, 207.Nm 208prints it before issuing the 209.Dq ready 210message. 211If the file 212.Pa /etc/ftpmotd 213exists, 214.Nm 215prints it after a successful login. Note the motd file used is the one 216relative to the login environment. This means the one in 217.Pa ~ftp/etc 218in the anonymous user's case. 219.Pp 220The ftp server currently supports the following ftp requests. 221The case of the requests is ignored. Requests marked [RW] are 222disabled if 223.Fl r 224is specified. 225.Bl -column "Request" -offset indent 226.It Sy Request Ta Sy "Description" 227.It ABOR Ta "abort previous command" 228.It ACCT Ta "specify account (ignored)" 229.It ALLO Ta "allocate storage (vacuously)" 230.It APPE Ta "append to a file [RW]" 231.It CDUP Ta "change to parent of current working directory" 232.It CWD Ta "change working directory" 233.It DELE Ta "delete a file [RW]" 234.It EPRT Ta "specify data connection port, multiprotocol" 235.It EPSV Ta "prepare for server-to-server transfer, multiprotocol" 236.It HELP Ta "give help information" 237.It LIST Ta "give list files in a directory" Pq Dq Li "ls -lgA" 238.It LPRT Ta "specify data connection port, multiprotocol" 239.It LPSV Ta "prepare for server-to-server transfer, multiprotocol" 240.It MDTM Ta "show last modification time of file" 241.It MKD Ta "make a directory [RW]" 242.It MODE Ta "specify data transfer" Em mode 243.It NLST Ta "give name list of files in directory" 244.It NOOP Ta "do nothing" 245.It PASS Ta "specify password" 246.It PASV Ta "prepare for server-to-server transfer" 247.It PORT Ta "specify data connection port" 248.It PWD Ta "print the current working directory" 249.It QUIT Ta "terminate session" 250.It REST Ta "restart incomplete transfer" 251.It RETR Ta "retrieve a file" 252.It RMD Ta "remove a directory [RW]" 253.It RNFR Ta "specify rename-from file name [RW]" 254.It RNTO Ta "specify rename-to file name [RW]" 255.It SITE Ta "non-standard commands (see next section)" 256.It SIZE Ta "return size of file" 257.It STAT Ta "return status of server" 258.It STOR Ta "store a file [RW]" 259.It STOU Ta "store a file with a unique name [RW]" 260.It STRU Ta "specify data transfer" Em structure 261.It SYST Ta "show operating system type of server system" 262.It TYPE Ta "specify data transfer" Em type 263.It USER Ta "specify user name" 264.It XCUP Ta "change to parent of current working directory (deprecated)" 265.It XCWD Ta "change working directory (deprecated)" 266.It XMKD Ta "make a directory (deprecated) [RW]" 267.It XPWD Ta "print the current working directory (deprecated)" 268.It XRMD Ta "remove a directory (deprecated) [RW]" 269.El 270.Pp 271The following non-standard or 272.Tn UNIX 273specific commands are supported 274by the 275SITE request. 276.Pp 277.Bl -column Request -offset indent 278.It Sy Request Ta Sy Description 279.It UMASK Ta change umask, e.g. ``SITE UMASK 002'' 280.It IDLE Ta set idle-timer, e.g. ``SITE IDLE 60'' 281.It CHMOD Ta "change mode of a file [RW], e.g. ``SITE CHMOD 755 filename''" 282.It MD5 Ta "report the files MD5 checksum, e.g. ``SITE MD5 filename''" 283.It HELP Ta give help information 284.El 285.Pp 286Note: SITE requests are disabled in case of anonymous logins. 287.Pp 288The remaining ftp requests specified in Internet RFC 959 289are 290recognized, but not implemented. 291MDTM and SIZE are not specified in RFC 959, but will appear in the 292next updated FTP RFC. 293To avoid possible denial-of-service attacks, SIZE requests against 294files larger than 10240 bytes will be denied if the current transfer 295type is ASCII. 296.Pp 297The ftp server will abort an active file transfer only when the 298ABOR 299command is preceded by a Telnet "Interrupt Process" (IP) 300signal and a Telnet "Synch" signal in the command Telnet stream, 301as described in Internet RFC 959. 302If a 303STAT 304command is received during a data transfer, preceded by a Telnet IP 305and Synch, transfer status will be returned. 306.Pp 307The 308.Nm 309utility interprets file names according to the 310.Dq globbing 311conventions used by 312.Xr csh 1 . 313This allows users to utilize the metacharacters 314.Dq Li \&*?[]{}~ . 315.Pp 316The 317.Nm 318utility authenticates users according to six rules. 319.Pp 320.Bl -enum -offset indent 321.It 322The login name must be in the password data base 323and not have a null password. 324In this case a password must be provided by the client before any 325file operations may be performed. 326If the user has an S/Key key, the response from a successful USER 327command will include an S/Key challenge. 328The client may choose to respond with a PASS command giving either 329a standard password or an S/Key one-time password. 330The server will automatically determine which type of 331password it has been given and attempt to authenticate accordingly. 332See 333.Xr key 1 334for more information on S/Key authentication. 335S/Key is a Trademark of Bellcore. 336.It 337The login name must not appear in the file 338.Pa /etc/ftpusers . 339.It 340The login name must not be a member of a group specified in the file 341.Pa /etc/ftpusers . 342Entries in this file interpreted as group names are prefixed by an "at" 343.Ql \&@ 344sign. 345.It 346The user must have a standard shell returned by 347.Xr getusershell 3 . 348.It 349If the user name appears in the file 350.Pa /etc/ftpchroot , 351or the user is a member of a group with a group entry in this file, 352i.e. one prefixed with 353.Ql \&@ , 354the session's root will be changed to the user's login directory by 355.Xr chroot 2 356as for an 357.Dq anonymous 358or 359.Dq ftp 360account (see next item). 361This facility may also be triggered by enabling the boolean "ftp-chroot" 362capability in 363.Xr login.conf 5 . 364However, the user must still supply a password. 365This feature is intended as a compromise between a fully anonymous 366account and a fully privileged account. 367The account should also be set up as for an anonymous account. 368.It 369If the user name is 370.Dq anonymous 371or 372.Dq ftp , 373an 374anonymous ftp account must be present in the password 375file (user 376.Dq ftp ) . 377In this case the user is allowed 378to log in by specifying any password (by convention an email address for 379the user should be used as the password). 380When the 381.Fl S 382option is set, all transfers are logged as well. 383.El 384.Pp 385In the last case, 386.Nm 387takes special measures to restrict the client's access privileges. 388The server performs a 389.Xr chroot 2 390to the home directory of the 391.Dq ftp 392user. 393In order that system security is not breached, it is recommended 394that the 395.Dq ftp 396subtree be constructed with care, following these rules: 397.Bl -tag -width "~ftp/pub" -offset indent 398.It Pa ~ftp 399Make the home directory owned by 400.Dq root 401and unwritable by anyone. 402.It Pa ~ftp/etc 403Make this directory owned by 404.Dq root 405and unwritable by anyone (mode 555). 406The files pwd.db (see 407.Xr passwd 5 ) 408and 409.Xr group 5 410must be present for the 411.Xr ls 1 412command to be able to produce owner names rather than numbers. 413The password field in 414.Xr passwd 415is not used, and should not contain real passwords. 416The file 417.Pa ftpmotd , 418if present, will be printed after a successful login. 419These files should be mode 444. 420.It Pa ~ftp/pub 421This directory and the subdirectories beneath it should be owned 422by the users and groups responsible for placing files in them, 423and be writable only by them (mode 755 or 775). 424They should 425.Em not 426be owned or writable by 427.Dq ftp 428or its group, otherwise guest users 429can fill the drive with unwanted files. 430.El 431.Pp 432If the system has multiple IP addresses, 433.Nm 434supports the idea of virtual hosts, which provides the ability to 435define multiple anonymous ftp areas, each one allocated to a different 436internet address. 437The file 438.Pa /etc/ftphosts 439contains information pertaining to each of the virtual hosts. 440Each host is defined on its own line which contains a number of 441fields separated by whitespace: 442.Bl -tag -offset indent -width hostname 443.It hostname 444Contains the hostname or IP address of the virtual host. 445.It user 446Contains a user record in the system password file. 447As with normal anonymous ftp, this user's access uid, gid and group 448memberships determine file access to the anonymous ftp area. 449The anonymous ftp area (to which any user is chrooted on login) 450is determined by the home directory defined for the account. 451User id and group for any ftp account may be the same as for the 452standard ftp user. 453.It statfile 454File to which all file transfers are logged, which 455defaults to 456.Pa /var/log/ftpd . 457.It welcome 458This file is the welcome message displayed before the server ready 459prompt. 460It defaults to 461.Pa /etc/ftpwelcome . 462.It motd 463This file is displayed after the user logs in. 464It defaults to 465.Pa /etc/ftpmotd . 466.El 467.Pp 468Lines beginning with a '#' are ignored and can be used to include 469comments. 470.Pp 471Defining a virtual host for the primary IP address or hostname 472changes the default for ftp logins to that address. 473The 'user', 'statfile', 'welcome' and 'motd' fields may be left 474blank, or a single hypen '-' used to indicate that the default 475value is to be used. 476.Pp 477As with any anonymous login configuration, due care must be given 478to setup and maintenance to guard against security related problems. 479.Pp 480The 481.Nm 482utility has internal support for handling remote requests to list 483files, and will not execute 484.Pa /bin/ls 485in either a chrooted or non-chrooted environment. The 486.Pa ~/bin/ls 487executable need not be placed into the chrooted tree, nor need the 488.Pa ~/bin 489directory exist. 490.Sh FILES 491.Bl -tag -width /etc/ftpwelcome -compact 492.It Pa /etc/ftpusers 493List of unwelcome/restricted users. 494.It Pa /etc/ftpchroot 495List of normal users who should be chroot'd. 496.It Pa /etc/ftphosts 497Virtual hosting configuration file. 498.It Pa /etc/ftpwelcome 499Welcome notice. 500.It Pa /etc/ftpmotd 501Welcome notice after login. 502.It Pa /var/run/nologin 503Displayed and access refused. 504.It Pa /var/log/ftpd 505Log file for anonymous transfers. 506.El 507.Sh SEE ALSO 508.Xr ftp 1 , 509.Xr key 1 , 510.Xr umask 2 , 511.Xr getusershell 3 , 512.Xr login.conf 5 , 513.Xr inetd 8 , 514.Xr syslogd 8 515.Sh BUGS 516The server must run as the super-user 517to create sockets with privileged port numbers. It maintains 518an effective user id of the logged in user, reverting to 519the super-user only when binding addresses to sockets. The 520possible security holes have been extensively 521scrutinized, but are possibly incomplete. 522.Sh HISTORY 523The 524.Nm 525utility appeared in 526.Bx 4.2 . 527IPv6 support was added in WIDE Hydrangea IPv6 stack kit. 528