1 .\" $NetBSD: ftpd.8,v 1.7 1995/04/11 02:44:53 cgd Exp $
3 .\" Copyright (c) 1985, 1988, 1991, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. All advertising materials mentioning features or use of this software
15 .\" must display the following acknowledgement:
16 .\" This product includes software developed by the University of
17 .\" California, Berkeley and its contributors.
18 .\" 4. Neither the name of the University nor the names of its contributors
19 .\" may be used to endorse or promote products derived from this software
20 .\" without specific prior written permission.
22 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
34 .\" @(#)ftpd.8 8.2 (Berkeley) 4/19/94
41 .Nd Internet File Transfer Protocol server
48 .Op Fl T Ar maxtimeout
50 .Op Fl u Ar default umask
51 .Op Fl B | Fl -builtin-ls
52 .Op Fl -good-chars= Ns Ar string
56 Internet File Transfer Protocol
57 server process. The server uses the
60 and listens at the port specified in the
62 service specification; see
68 Select the level of authentication required. Kerberised login can not
69 be turned off. The default is to only allow kerberised login. Other
70 possibilities can be turned on by giving a string of comma separated
76 Allow logging in with plaintext password. The password can be a(n) OTP
77 or an ordinary password.
81 but only OTP is allowed.
83 Allow anonymous login.
86 The following combination modes exists for backwards compatibility:
98 Debugging information is written to the syslog using LOG_FTP.
100 Anonymous users will get a umask of
103 Open a socket and wait for a connection. This is mainly used for
104 debugging when ftpd isn't started by inetd.
106 Each successful and failed
108 session is logged using syslog with a facility of LOG_FTP.
109 If this option is specified twice, the retrieve (get), store (put), append,
110 delete, make directory, remove directory and rename operations and
111 their filename arguments are also logged.
115 (a service name or number) instead of the default
118 A client may also request a different timeout period;
119 the maximum period allowed may be set to
124 The default limit is 2 hours.
126 The inactivity timeout period is set to
128 seconds (the default is 15 minutes).
130 Set the initial umask to something else than the default 027.
132 In previous versions of
134 when a passive mode client requested a data connection to the server, the
135 server would use data ports in the range 1024..4999. Now, by default,
136 if the system supports the IP_PORTRANGE socket option, the server will
137 use data ports in the range 49152..65535. Specifying this option will
138 revert to the old behavior.
145 use built-in ls to list files
147 .Fl -good-chars= Ns Ar string
149 allowed anonymous upload filename chars
154 can be used to disable ftp access.
157 displays it and exits.
162 prints it before issuing the
169 prints it after a successful login.
171 The ftp server currently supports the following ftp requests.
172 The case of the requests is ignored.
173 .Bl -column "Request" -offset indent
174 .It Request Ta "Description"
175 .It ABOR Ta "abort previous command"
176 .It ACCT Ta "specify account (ignored)"
177 .It ALLO Ta "allocate storage (vacuously)"
178 .It APPE Ta "append to a file"
179 .It CDUP Ta "change to parent of current working directory"
180 .It CWD Ta "change working directory"
181 .It DELE Ta "delete a file"
182 .It HELP Ta "give help information"
183 .It LIST Ta "give list files in a directory" Pq Dq Li "ls -lgA"
184 .It MKD Ta "make a directory"
185 .It MDTM Ta "show last modification time of file"
186 .It MODE Ta "specify data transfer" Em mode
187 .It NLST Ta "give name list of files in directory"
188 .It NOOP Ta "do nothing"
189 .It PASS Ta "specify password"
190 .It PASV Ta "prepare for server-to-server transfer"
191 .It PORT Ta "specify data connection port"
192 .It PWD Ta "print the current working directory"
193 .It QUIT Ta "terminate session"
194 .It REST Ta "restart incomplete transfer"
195 .It RETR Ta "retrieve a file"
196 .It RMD Ta "remove a directory"
197 .It RNFR Ta "specify rename-from file name"
198 .It RNTO Ta "specify rename-to file name"
199 .It SITE Ta "non-standard commands (see next section)"
200 .It SIZE Ta "return size of file"
201 .It STAT Ta "return status of server"
202 .It STOR Ta "store a file"
203 .It STOU Ta "store a file with a unique name"
204 .It STRU Ta "specify data transfer" Em structure
205 .It SYST Ta "show operating system type of server system"
206 .It TYPE Ta "specify data transfer" Em type
207 .It USER Ta "specify user name"
208 .It XCUP Ta "change to parent of current working directory (deprecated)"
209 .It XCWD Ta "change working directory (deprecated)"
210 .It XMKD Ta "make a directory (deprecated)"
211 .It XPWD Ta "print the current working directory (deprecated)"
212 .It XRMD Ta "remove a directory (deprecated)"
215 The following commands are specified by RFC2228.
216 .Bl -column Request -offset indent
217 .It AUTH Ta "authentication/security mechanism"
218 .It ADAT Ta "authentication/security data"
219 .It PROT Ta "data channel protection level"
220 .It PBSZ Ta "protection buffer size"
221 .It MIC Ta "integrity protected command"
222 .It CONF Ta "confidentiality protected command"
223 .It ENC Ta "privacy protected command"
224 .It CCC Ta "clear command channel"
227 The following non-standard or
229 specific commands are supported
233 .Bl -column Request -offset indent
234 .It UMASK Ta change umask, (e.g.
235 .Ic "SITE UMASK 002" )
236 .It IDLE Ta set idle-timer, (e.g.
238 .It CHMOD Ta change mode of a file (e.g.
239 .Ic "SITE CHMOD 755 filename" )
240 .It FIND Ta quickly find a specific file with GNU
242 .It HELP Ta give help information.
245 The following Kerberos related site commands are understood.
246 .Bl -column Request -offset indent
247 .It KAUTH Ta obtain remote tickets.
248 .It KLIST Ta show remote tickets
251 The remaining ftp requests specified in Internet RFC 959
253 recognized, but not implemented.
254 MDTM and SIZE are not specified in RFC 959, but will appear in the
255 next updated FTP RFC.
257 The ftp server will abort an active file transfer only when the
259 command is preceded by a Telnet "Interrupt Process" (IP)
260 signal and a Telnet "Synch" signal in the command Telnet stream,
261 as described in Internet RFC 959.
264 command is received during a data transfer, preceded by a Telnet IP
265 and Synch, transfer status will be returned.
268 interprets file names according to the
272 This allows users to utilize the metacharacters
276 authenticates users according to these rules.
278 .Bl -enum -offset indent
280 If Kerberos authentication is used, the user must pass valid tickets
281 and the principal must be allowed to login as the remote user.
283 The login name must be in the password data base, and not have a null
284 password (if kerberos is used the password field is not checked). In
285 this case a password must be provided by the client before any file
286 operations may be performed. If the user has an OTP key, the response
287 from a successful USER command will include an OTP challenge. The
288 client may choose to respond with a PASS command giving either a
289 standard password or an OTP one-time password. The server will
290 automatically determine which type of password it has been given and
291 attempt to authenticate accordingly. See
293 for more information on OTP authentication.
295 The login name must not appear in the file
298 The user must have a standard shell returned by
301 If the user name appears in the file
303 the session's root will be changed to the user's login directory by
309 account (see next item). However, the user must still supply a password.
310 This feature is intended as a compromise between a fully anonymous account
311 and a fully privileged account. The account should also be set up as for an
319 anonymous ftp account must be present in the password
322 In this case the user is allowed
323 to log in by specifying any password (by convention an email address for
324 the user should be used as the password).
329 takes special measures to restrict the client's access privileges.
330 The server performs a
332 to the home directory of the
335 In order that system security is not breached, it is recommended
338 subtree be constructed with care, consider following these guidelines
341 In general all files should be owned by
343 and have non-write permissions (644 or 755 depending on the kind of
344 file). No files should be owned or writable by
346 (possibly with exception for the
349 .Bl -tag -width "~ftp/pub" -offset indent
353 homedirectory should be owned by root.
355 The directory for external programs (such as
357 These programs must either be statically linked, or you must setup an
358 environment for dynamic linking when running chrooted.
359 These programs will be used if present:
360 .Bl -tag -width "locate" -offset indent
362 Used when listing files.
364 When retrieving a filename that ends in
366 and that file isn't present,
368 will try to find the filename without
370 and compress it on the fly.
372 Same as compress, just with files ending in
375 Enables retrieval of whole directories as files ending in
377 Can also be combined with compression. You must use GNU Tar (or some
378 other that supports the
384 Will enable ``fast find'' with the
386 command. You must also create a
392 If you put copies of the
396 files here, ls will be able to produce owner names rather than
397 numbers. Remember to remove any passwords from these files.
401 if present, will be printed after a successful login.
407 Traditional place to put whatever you want to make public.
410 If you want guests to be able to upload files, create a
416 with mode 730 (make sure
420 The following restrictions apply to anonymous users:
423 Directories created will have mode 700.
425 Uploaded files will be created with an umask of 777, if not changed
430 These command are not accessible:
431 .Ic DELE , RMD , RNTO , RNFR ,
436 Filenames must start with an alpha-numeric character, and consist of
437 alpha-numeric characters or any of the following:
452 .Bl -tag -width /etc/ftpwelcome -compact
454 Access list for users.
455 .It Pa /etc/ftpchroot
456 List of normal users who should be chroot'd.
457 .It Pa /etc/ftpwelcome
460 Welcome notice after login.
462 Displayed and access refused.
464 Login access for Kerberos.
473 .Bl -tag -compact -width "RFC 1938"
475 FTP PROTOCOL SPECIFICATION
479 FTP Security Extensions.
482 The server must run as the super-user
483 to create sockets with privileged port numbers. It maintains
484 an effective user id of the logged in user, reverting to
485 the super-user only when binding addresses to sockets. The
486 possible security holes have been extensively
487 scrutinized, but are possibly incomplete.