ftpd.8 (99195) | ftpd.8 (99500) |
---|---|
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. --- 16 unchanged lines hidden (view full) --- 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 | 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. --- 16 unchanged lines hidden (view full) --- 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: head/libexec/ftpd/ftpd.8 99195 2002-07-01 02:30:11Z mdodd $ | 33.\" $FreeBSD: head/libexec/ftpd/ftpd.8 99500 2002-07-06 19:19:48Z charnier $ |
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 46ADEMORSUdro 44.Op Fl l Op Fl l 45.Op Fl T Ar maxtimeout 46.Op Fl a Ar address 47.Op Fl p Ar file 48.Op Fl t Ar timeout 49.Sh DESCRIPTION | 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 46ADEMORSUdro 44.Op Fl l Op Fl l 45.Op Fl T Ar maxtimeout 46.Op Fl a Ar address 47.Op Fl p Ar file 48.Op Fl t Ar timeout 49.Sh DESCRIPTION |
50.Nm Ftpd 51is the | 50The 51.Nm 52utility is the |
52Internet File Transfer Protocol 53server process. The server uses the 54.Tn TCP 55protocol 56and listens at the port specified in the 57.Dq ftp 58service specification; see 59.Xr services 5 . --- 216 unchanged lines hidden (view full) --- 276command is preceded by a Telnet "Interrupt Process" (IP) 277signal and a Telnet "Synch" signal in the command Telnet stream, 278as described in Internet RFC 959. 279If a 280STAT 281command is received during a data transfer, preceded by a Telnet IP 282and Synch, transfer status will be returned. 283.Pp | 53Internet File Transfer Protocol 54server process. The server uses the 55.Tn TCP 56protocol 57and listens at the port specified in the 58.Dq ftp 59service specification; see 60.Xr services 5 . --- 216 unchanged lines hidden (view full) --- 277command is preceded by a Telnet "Interrupt Process" (IP) 278signal and a Telnet "Synch" signal in the command Telnet stream, 279as described in Internet RFC 959. 280If a 281STAT 282command is received during a data transfer, preceded by a Telnet IP 283and Synch, transfer status will be returned. 284.Pp |
284.Nm Ftpd 285interprets file names according to the | 285The 286.Nm 287utility interprets file names according to the |
286.Dq globbing 287conventions used by 288.Xr csh 1 . 289This allows users to utilize the metacharacters 290.Dq Li \&*?[]{}~ . 291.Pp | 288.Dq globbing 289conventions used by 290.Xr csh 1 . 291This allows users to utilize the metacharacters 292.Dq Li \&*?[]{}~ . 293.Pp |
292.Nm Ftpd 293authenticates users according to six rules. | 294The 295.Nm 296utility authenticates users according to six rules. |
294.Pp 295.Bl -enum -offset indent 296.It 297The login name must be in the password data base 298and not have a null password. 299In this case a password must be provided by the client before any 300file operations may be performed. 301If the user has an S/Key key, the response from a successful USER --- 76 unchanged lines hidden (view full) --- 378Make this directory owned by 379.Dq root 380and unwritable by anyone (mode 555). 381The files pwd.db (see 382.Xr passwd 5 ) 383and 384.Xr group 5 385must be present for the | 297.Pp 298.Bl -enum -offset indent 299.It 300The login name must be in the password data base 301and not have a null password. 302In this case a password must be provided by the client before any 303file operations may be performed. 304If the user has an S/Key key, the response from a successful USER --- 76 unchanged lines hidden (view full) --- 381Make this directory owned by 382.Dq root 383and unwritable by anyone (mode 555). 384The files pwd.db (see 385.Xr passwd 5 ) 386and 387.Xr group 5 388must be present for the |
386.Xr ls | 389.Xr ls 1 |
387command to be able to produce owner names rather than numbers. 388The password field in 389.Xr passwd 390is not used, and should not contain real passwords. 391The file 392.Pa ftpmotd , 393if present, will be printed after a successful login. 394These files should be mode 444. --- 52 unchanged lines hidden (view full) --- 447changes the default for ftp logins to that address. 448The 'user', 'statfile', 'welcome' and 'motd' fields may be left 449blank, or a single hypen '-' used to indicate that the default 450value is to be used. 451.Pp 452As with any anonymous login configuration, due care must be given 453to setup and maintenance to guard against security related problems. 454.Pp | 390command to be able to produce owner names rather than numbers. 391The password field in 392.Xr passwd 393is not used, and should not contain real passwords. 394The file 395.Pa ftpmotd , 396if present, will be printed after a successful login. 397These files should be mode 444. --- 52 unchanged lines hidden (view full) --- 450changes the default for ftp logins to that address. 451The 'user', 'statfile', 'welcome' and 'motd' fields may be left 452blank, or a single hypen '-' used to indicate that the default 453value is to be used. 454.Pp 455As with any anonymous login configuration, due care must be given 456to setup and maintenance to guard against security related problems. 457.Pp |
458The |
|
455.Nm | 459.Nm |
456has internal support for handling remote requests to list | 460utility has internal support for handling remote requests to list |
457files, and will not execute 458.Pa /bin/ls 459in either a chrooted or non-chrooted environment. The 460.Pa ~/bin/ls 461executable need not be placed into the chrooted tree, nor need the 462.Pa ~/bin 463directory exist. 464.Sh FILES --- 25 unchanged lines hidden (view full) --- 490to create sockets with privileged port numbers. It maintains 491an effective user id of the logged in user, reverting to 492the super-user only when binding addresses to sockets. The 493possible security holes have been extensively 494scrutinized, but are possibly incomplete. 495.Sh HISTORY 496The 497.Nm | 461files, and will not execute 462.Pa /bin/ls 463in either a chrooted or non-chrooted environment. The 464.Pa ~/bin/ls 465executable need not be placed into the chrooted tree, nor need the 466.Pa ~/bin 467directory exist. 468.Sh FILES --- 25 unchanged lines hidden (view full) --- 494to create sockets with privileged port numbers. It maintains 495an effective user id of the logged in user, reverting to 496the super-user only when binding addresses to sockets. The 497possible security holes have been extensively 498scrutinized, but are possibly incomplete. 499.Sh HISTORY 500The 501.Nm |
498command appeared in | 502utility appeared in |
499.Bx 4.2 . 500IPv6 support was added in WIDE Hydrangea IPv6 stack kit. | 503.Bx 4.2 . 504IPv6 support was added in WIDE Hydrangea IPv6 stack kit. |