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 April 20, 2007 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 468ADdEhMmOoRrSUvW 44.Op Fl l Op Fl l 45.Op Fl a Ar address 46.Op Fl P Ar port 47.Op Fl p Ar file 48.Op Fl T Ar maxtimeout 49.Op Fl t Ar timeout 50.Op Fl u Ar umask 51.Sh DESCRIPTION 52The 53.Nm 54utility is the 55Internet File Transfer Protocol 56server process. 57The server uses the 58.Tn TCP 59protocol 60and listens at the port specified with the 61.Fl P 62option or in the 63.Dq ftp 64service specification; see 65.Xr services 5 . 66.Pp 67Available options: 68.Bl -tag -width indent 69.It Fl 4 70When 71.Fl D 72is specified, accept connections via 73.Dv AF_INET 74socket. 75.It Fl 6 76When 77.Fl D 78is specified, accept connections via 79.Dv AF_INET6 80socket. 81.It Fl 8 82Enable transparent UTF-8 mode. 83RFC\ 2640 compliant clients will be told that the character encoding 84used by the server is UTF-8, which is the only effect of the option. 85.Pp 86This option does not enable any encoding conversion for server file names; 87it implies instead that the names of files on the server are encoded 88in UTF-8. 89As for files uploaded via FTP, it is the duty of the RFC\ 2640 compliant 90client to convert their names from the client's local encoding to UTF-8. 91FTP command names and own 92.Nm 93messages are always encoded in ASCII, which is a subset of UTF-8. 94Hence no need for server-side conversion at all. 95.It Fl A 96Allow only anonymous ftp access. 97.It Fl a 98When 99.Fl D 100is specified, accept connections only on the specified 101.Ar address . 102.It Fl D 103With this option set, 104.Nm 105will detach and become a daemon, accepting connections on the FTP port and 106forking children processes to handle them. 107This is lower overhead than starting 108.Nm 109from 110.Xr inetd 8 111and is thus useful on busy servers to reduce load. 112.It Fl d 113Debugging information is written to the syslog using 114.Dv LOG_FTP . 115.It Fl E 116Disable the EPSV command. 117This is useful for servers behind older firewalls. 118.It Fl h 119Disable printing host-specific information, such as the 120server software version or hostname, in server messages. 121.It Fl l 122Each successful and failed 123.Xr ftp 1 124session is logged using syslog with a facility of 125.Dv LOG_FTP . 126If this option is specified twice, the retrieve (get), store (put), append, 127delete, make directory, remove directory and rename operations and 128their filename arguments are also logged. 129By default, 130.Xr syslogd 8 131logs these to 132.Pa /var/log/xferlog . 133.It Fl M 134Prevent anonymous users from creating directories. 135.It Fl m 136Permit anonymous users to overwrite or modify 137existing files if allowed by file system permissions. 138By default, anonymous users cannot modify existing files; 139in particular, files to upload will be created under a unique name. 140.It Fl O 141Put server in write-only mode for anonymous users only. 142RETR is disabled for anonymous users, preventing anonymous downloads. 143This has no effect if 144.Fl o 145is also specified. 146.It Fl o 147Put server in write-only mode. 148RETR is disabled, preventing downloads. 149.It Fl P 150When 151.Fl D 152is specified, accept connections at 153.Ar port , 154specified as a numeric value or service name, instead of at the default 155.Dq ftp 156port. 157.It Fl p 158When 159.Fl D 160is specified, write the daemon's process ID to 161.Ar file 162instead of the default pid file, 163.Pa /var/run/ftpd.pid . 164.It Fl R 165With this option set, 166.Nm 167will revert to historical behavior with regard to security checks on 168user operations and restrictions on PORT requests. 169Currently, 170.Nm 171will only honor PORT commands directed to unprivileged ports on the 172remote user's host (which violates the FTP protocol specification but 173closes some security holes). 174.It Fl r 175Put server in read-only mode. 176All commands which may modify the local file system are disabled. 177.It Fl S 178With this option set, 179.Nm 180logs all anonymous file downloads to the file 181.Pa /var/log/ftpd 182when this file exists. 183.It Fl T 184A client may also request a different timeout period; 185the maximum period allowed may be set to 186.Ar timeout 187seconds with the 188.Fl T 189option. 190The default limit is 2 hours. 191.It Fl t 192The inactivity timeout period is set to 193.Ar timeout 194seconds (the default is 15 minutes). 195.It Fl U 196This option instructs ftpd to use data ports in the range of 197.Dv IP_PORTRANGE_DEFAULT 198instead of in the range of 199.Dv IP_PORTRANGE_HIGH . 200Such a change may be useful for some specific firewall configurations; 201see 202.Xr ip 4 203for more information. 204.Pp 205Note that option is a virtual no-op in 206.Fx 5.0 207and above; both port 208ranges are indentical by default. 209.It Fl u 210The default file creation mode mask is set to 211.Ar umask , 212which is expected to be an octal numeric value. 213Refer to 214.Xr umask 2 215for details. 216This option may be overridden by 217.Xr login.conf 5 . 218.It Fl v 219A synonym for 220.Fl d . 221.It Fl W 222Do not log FTP sessions to 223.Pa /var/log/wtmp . 224.El 225.Pp 226The file 227.Pa /var/run/nologin 228can be used to disable ftp access. 229If the file exists, 230.Nm 231displays it and exits. 232If the file 233.Pa /etc/ftpwelcome 234exists, 235.Nm 236prints it before issuing the 237.Dq ready 238message. 239If the file 240.Pa /etc/ftpmotd 241exists, 242.Nm 243prints it after a successful login. 244Note the motd file used is the one 245relative to the login environment. 246This means the one in 247.Pa ~ftp/etc 248in the anonymous user's case. 249.Pp 250The ftp server currently supports the following ftp requests. 251The case of the requests is ignored. 252Requests marked [RW] are 253disabled if 254.Fl r 255is specified. 256.Bl -column "Request" -offset indent 257.It Sy Request Ta Sy "Description" 258.It ABOR Ta "abort previous command" 259.It ACCT Ta "specify account (ignored)" 260.It ALLO Ta "allocate storage (vacuously)" 261.It APPE Ta "append to a file [RW]" 262.It CDUP Ta "change to parent of current working directory" 263.It CWD Ta "change working directory" 264.It DELE Ta "delete a file [RW]" 265.It EPRT Ta "specify data connection port, multiprotocol" 266.It EPSV Ta "prepare for server-to-server transfer, multiprotocol" 267.It FEAT Ta "give information on extended features of server" 268.It HELP Ta "give help information" 269.It LIST Ta "give list files in a directory" Pq Dq Li "ls -lgA" 270.It LPRT Ta "specify data connection port, multiprotocol" 271.It LPSV Ta "prepare for server-to-server transfer, multiprotocol" 272.It MDTM Ta "show last modification time of file" 273.It MKD Ta "make a directory [RW]" 274.It MODE Ta "specify data transfer" Em mode 275.It NLST Ta "give name list of files in directory" 276.It NOOP Ta "do nothing" 277.It PASS Ta "specify password" 278.It PASV Ta "prepare for server-to-server transfer" 279.It PORT Ta "specify data connection port" 280.It PWD Ta "print the current working directory" 281.It QUIT Ta "terminate session" 282.It REST Ta "restart incomplete transfer" 283.It RETR Ta "retrieve a file" 284.It RMD Ta "remove a directory [RW]" 285.It RNFR Ta "specify rename-from file name [RW]" 286.It RNTO Ta "specify rename-to file name [RW]" 287.It SITE Ta "non-standard commands (see next section)" 288.It SIZE Ta "return size of file" 289.It STAT Ta "return status of server" 290.It STOR Ta "store a file [RW]" 291.It STOU Ta "store a file with a unique name [RW]" 292.It STRU Ta "specify data transfer" Em structure 293.It SYST Ta "show operating system type of server system" 294.It TYPE Ta "specify data transfer" Em type 295.It USER Ta "specify user name" 296.It XCUP Ta "change to parent of current working directory (deprecated)" 297.It XCWD Ta "change working directory (deprecated)" 298.It XMKD Ta "make a directory (deprecated) [RW]" 299.It XPWD Ta "print the current working directory (deprecated)" 300.It XRMD Ta "remove a directory (deprecated) [RW]" 301.El 302.Pp 303The following non-standard or 304.Ux 305specific commands are supported 306by the 307SITE request. 308.Pp 309.Bl -column Request -offset indent 310.It Sy Request Ta Sy Description 311.It UMASK Ta change umask, e.g. ``SITE UMASK 002'' 312.It IDLE Ta set idle-timer, e.g. ``SITE IDLE 60'' 313.It CHMOD Ta "change mode of a file [RW], e.g. ``SITE CHMOD 755 filename''" 314.It MD5 Ta "report the files MD5 checksum, e.g. ``SITE MD5 filename''" 315.It HELP Ta give help information 316.El 317.Pp 318Note: SITE requests are disabled in case of anonymous logins. 319.Pp 320The remaining ftp requests specified in Internet RFC 959 321are 322recognized, but not implemented. 323MDTM and SIZE are not specified in RFC 959, but will appear in the 324next updated FTP RFC. 325To avoid possible denial-of-service attacks, SIZE requests against 326files larger than 10240 bytes will be denied if the current transfer 327type is ASCII. 328.Pp 329The ftp server will abort an active file transfer only when the 330ABOR 331command is preceded by a Telnet "Interrupt Process" (IP) 332signal and a Telnet "Synch" signal in the command Telnet stream, 333as described in Internet RFC 959. 334If a 335STAT 336command is received during a data transfer, preceded by a Telnet IP 337and Synch, transfer status will be returned. 338.Pp 339The 340.Nm 341utility interprets file names according to the 342.Dq globbing 343conventions used by 344.Xr csh 1 . 345This allows users to utilize the metacharacters 346.Dq Li \&*?[]{}~ . 347.Pp 348The 349.Nm 350utility authenticates users according to six rules. 351.Pp 352.Bl -enum -offset indent 353.It 354The login name must be in the password data base 355and not have a null password. 356In this case a password must be provided by the client before any 357file operations may be performed. 358If the user has an OPIE key, the response from a successful USER 359command will include an OPIE challenge. 360The client may choose to respond with a PASS command giving either 361a standard password or an OPIE one-time password. 362The server will automatically determine which type of 363password it has been given and attempt to authenticate accordingly. 364See 365.Xr opie 4 366for more information on OPIE authentication. 367.It 368The login name must not appear in the file 369.Pa /etc/ftpusers . 370.It 371The login name must not be a member of a group specified in the file 372.Pa /etc/ftpusers . 373Entries in this file interpreted as group names are prefixed by an "at" 374.Ql \&@ 375sign. 376.It 377The user must have a standard shell returned by 378.Xr getusershell 3 . 379.It 380If the user name appears in the file 381.Pa /etc/ftpchroot , 382or the user is a member of a group with a group entry in this file, 383i.e., one prefixed with 384.Ql \&@ , 385the session's root will be changed to the directory specified 386in this file or to the user's login directory by 387.Xr chroot 2 388as for an 389.Dq anonymous 390or 391.Dq ftp 392account (see next item). 393See 394.Xr ftpchroot 5 395for a detailed description of the format of this file. 396This facility may also be triggered by enabling the boolean "ftp-chroot" 397capability in 398.Xr login.conf 5 . 399However, the user must still supply a password. 400This feature is intended as a compromise between a fully anonymous 401account and a fully privileged account. 402The account should also be set up as for an anonymous account. 403.It 404If the user name is 405.Dq anonymous 406or 407.Dq ftp , 408an 409anonymous ftp account must be present in the password 410file (user 411.Dq ftp ) . 412In this case the user is allowed 413to log in by specifying any password (by convention an email address for 414the user should be used as the password). 415When the 416.Fl S 417option is set, all transfers are logged as well. 418.El 419.Pp 420In the last case, 421.Nm 422takes special measures to restrict the client's access privileges. 423The server performs a 424.Xr chroot 2 425to the home directory of the 426.Dq ftp 427user. 428As a special case if the 429.Dq ftp 430user's home directory pathname contains the 431.Pa /./ 432separator, 433.Nm 434uses its left-hand side as the name of the directory to do 435.Xr chroot 2 436to, and its right-hand side to change the current directory to afterwards. 437A typical example for this case would be 438.Pa /usr/local/ftp/./pub . 439In order that system security is not breached, it is recommended 440that the 441.Dq ftp 442subtree be constructed with care, following these rules: 443.Bl -tag -width "~ftp/pub" -offset indent 444.It Pa ~ftp 445Make the home directory owned by 446.Dq root 447and unwritable by anyone. 448.It Pa ~ftp/etc 449Make this directory owned by 450.Dq root 451and unwritable by anyone (mode 555). 452The files pwd.db (see 453.Xr passwd 5 ) 454and 455.Xr group 5 456must be present for the 457.Xr ls 1 458command to be able to produce owner names rather than numbers. 459The password field in 460.Xr passwd 5 461is not used, and should not contain real passwords. 462The file 463.Pa ftpmotd , 464if present, will be printed after a successful login. 465These files should be mode 444. 466.It Pa ~ftp/pub 467This directory and the subdirectories beneath it should be owned 468by the users and groups responsible for placing files in them, 469and be writable only by them (mode 755 or 775). 470They should 471.Em not 472be owned or writable by 473.Dq ftp 474or its group, otherwise guest users 475can fill the drive with unwanted files. 476.El 477.Pp 478If the system has multiple IP addresses, 479.Nm 480supports the idea of virtual hosts, which provides the ability to 481define multiple anonymous ftp areas, each one allocated to a different 482internet address. 483The file 484.Pa /etc/ftphosts 485contains information pertaining to each of the virtual hosts. 486Each host is defined on its own line which contains a number of 487fields separated by whitespace: 488.Bl -tag -offset indent -width hostname 489.It hostname 490Contains the hostname or IP address of the virtual host. 491.It user 492Contains a user record in the system password file. 493As with normal anonymous ftp, this user's access uid, gid and group 494memberships determine file access to the anonymous ftp area. 495The anonymous ftp area (to which any user is chrooted on login) 496is determined by the home directory defined for the account. 497User id and group for any ftp account may be the same as for the 498standard ftp user. 499.It statfile 500File to which all file transfers are logged, which 501defaults to 502.Pa /var/log/ftpd . 503.It welcome 504This file is the welcome message displayed before the server ready 505prompt. 506It defaults to 507.Pa /etc/ftpwelcome . 508.It motd 509This file is displayed after the user logs in. 510It defaults to 511.Pa /etc/ftpmotd . 512.El 513.Pp 514Lines beginning with a '#' are ignored and can be used to include 515comments. 516.Pp 517Defining a virtual host for the primary IP address or hostname 518changes the default for ftp logins to that address. 519The 'user', 'statfile', 'welcome' and 'motd' fields may be left 520blank, or a single hyphen '-' used to indicate that the default 521value is to be used. 522.Pp 523As with any anonymous login configuration, due care must be given 524to setup and maintenance to guard against security related problems. 525.Pp 526The 527.Nm 528utility has internal support for handling remote requests to list 529files, and will not execute 530.Pa /bin/ls 531in either a chrooted or non-chrooted environment. 532The 533.Pa ~/bin/ls 534executable need not be placed into the chrooted tree, nor need the 535.Pa ~/bin 536directory exist. 537.Sh FILES 538.Bl -tag -width ".Pa /var/run/ftpd.pid" -compact 539.It Pa /etc/ftpusers 540List of unwelcome/restricted users. 541.It Pa /etc/ftpchroot 542List of normal users who should be chroot'd. 543.It Pa /etc/ftphosts 544Virtual hosting configuration file. 545.It Pa /etc/ftpwelcome 546Welcome notice. 547.It Pa /etc/ftpmotd 548Welcome notice after login. 549.It Pa /var/run/ftpd.pid 550Default pid file for daemon mode. 551.It Pa /var/run/nologin 552Displayed and access refused. 553.It Pa /var/log/ftpd 554Log file for anonymous transfers. 555.It Pa /var/log/xferlog 556Default place for session logs. 557.El 558.Sh SEE ALSO 559.Xr ftp 1 , 560.Xr umask 2 , 561.Xr getusershell 3 , 562.Xr opie 4 , 563.Xr ftpchroot 5 , 564.Xr login.conf 5 , 565.Xr inetd 8 , 566.Xr syslogd 8 567.Sh HISTORY 568The 569.Nm 570utility appeared in 571.Bx 4.2 . 572IPv6 support was added in WIDE Hydrangea IPv6 stack kit. 573.Sh BUGS 574The server must run as the super-user 575to create sockets with privileged port numbers. 576It maintains 577an effective user id of the logged in user, reverting to 578the super-user only when binding addresses to sockets. 579The 580possible security holes have been extensively 581scrutinized, but are possibly incomplete. 582