1 .\" -*- nroff -*- --------------------------------------------------------- *
4 .\" Copyright (c) 1990, 1993, 1994
5 .\" The Regents of the University of California. All rights reserved.
7 .\" Copyright 2001 H. Peter Anvin - All Rights Reserved
9 .\" Redistribution and use in source and binary forms, with or without
10 .\" modification, are permitted provided that the following conditions
12 .\" 1. Redistributions of source code must retain the above copyright
13 .\" notice, this list of conditions and the following disclaimer.
14 .\" 2. Redistributions in binary form must reproduce the above copyright
15 .\" notice, this list of conditions and the following disclaimer in the
16 .\" documentation and/or other materials provided with the distribution.
17 .\" 3. Neither the name of the University nor the names of its contributors
18 .\" may be used to endorse or promote products derived from this software
19 .\" without specific prior written permission.
21 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
22 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
23 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
24 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
25 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
26 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
27 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
28 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
29 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
30 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33 .\"----------------------------------------------------------------------- */
34 .TH TFTPD 8 "23 October 2002" "tftp-hpa @@VERSION@@" "System Manager's Manual"
37 \- IPv4 Trivial File Transfer Protocol server
44 is a server for the IPv4 Trivial File Transfer Protocol. The TFTP
45 protocol is extensively used to support remote booting of diskless
46 devices. The server is normally started by
48 but can also run standalone.
53 Run the server in standalone (listen) mode, rather than run from
57 option is ignored, and the
59 option can be used to specify a specific local address or port to
62 \fB\-a\fP \fI[address][:port]\fP
67 to listen to when called with the
69 option. The default is to listen to the
73 on all local addresses.
76 Allow new files to be created. By default,
78 will only allow upload of files that already exist. Files are created
79 with default permissions allowing anyone to read or write them, unless
84 options are specified.
87 Change root directory on startup. This means the remote host does not
88 need to pass along the directory as part of the transfer, and may add
91 is specified, exactly one
93 should be specified on the command line. The use of this option is
94 recommended for security as well as compatibility with some boot ROMs
95 which cannot be easily made to include a directory name in its request.
97 \fB\-u\fP \fIusername\fP
98 Specify the username which
100 will run as; the default is "nobody". The user ID, group ID, and (if
101 possible on the platform) the supplementary group IDs will be set to
102 the ones specified in the system permission database for this
105 \fB\-U\fP \fIumask\fP
106 Sets the \fIumask\fP for newly created files to the specified value.
107 The default is zero (anyone can read or write) if the
109 option is not specified, or inherited from the invoking process if
114 Perform no additional permissions checks above the normal
115 system-provided access controls for the user specified via the
119 \fB\-t\fP \fItimeout\fP
122 this specifies how long, in seconds, to wait for a second connection
123 before terminating the server.
125 will then respawn the server when another request comes in. The
126 default is 900 (15 minutes.)
128 \fB\-T\fP \fItimeout\fP
129 Determine the default timeout, in microseconds, before the first
130 packet is retransmitted. This can be modified by the client if the
134 option is negotiated. The default is 1000000 (1 second.)
136 \fB\-m\fP \fIremap-file\fP
137 Specify the use of filename remapping. The
139 is a file containing the remapping rules. See the section on filename
140 remapping below. This option may not be compiled in, see the output of
142 to verify whether or not it is available.
145 Increase the logging verbosity of
147 This flag can be specified multiple times for even higher verbosity.
149 \fB\-r\fP \fItftp-option\fP
150 Indicate that a specific RFC 2347 TFTP option should never be
154 Print the version number and configuration to standard output, then
156 .SH "RFC 2347 OPTION NEGOTIATION"
159 supports RFC 2347 option negotation. Currently implemented options
162 \fBblksize\fP (RFC 2348)
163 Set the transfer block size to anything less than or equal to the
164 specified option. This version of
166 can support any block size up to the theoretical maximum of 65464
169 \fBblksize2\fP (nonstandard)
170 Set the transfer block size to anything less than or equal to the
171 specified option, but restrict the possible responses to powers of 2.
172 The maximum is 32768 bytes (the largest power of 2 less than or equal
175 \fBtsize\fP (RFC 2349)
176 Report the size of the file that is about to be transferred. This
181 option for binary (octet) mode transfers.
183 \fBtimeout\fP (RFC 2349)
184 Set the time before the server retransmits a packet, in seconds.
186 \fButimeout\fP (nonstandard)
187 Set the time before the server retransmits a packet, in microseconds.
192 option can be used to disable specific options; this may be necessary
193 to work around bugs in specific TFTP client implementations. For
194 example, some TFTP clients have been found to request the
196 option, but crash with an error if they actually get the option
197 accepted by the server.
198 .SH "FILENAME REMAPPING"
201 option specifies a file which contains filename remapping rules. Each
202 non-comment line (comments begin with hash marks,
208 a regular expression in the style of
211 .IR "replacement pattern" .
212 The operation indicated by
216 matches all or part of the filename. Rules are processed from the top
217 down, and by default, all rules are processed even if there is a
222 can be any combination of the following letters:
225 Replace the substring matched by
228 .IR "replacement pattern" .
229 The replacement pattern may contain escape sequences; see below.
232 Repeat this rule until it no longer matches. This is always used with
238 case-insensitively. By default it is case sensitive.
241 If this rule matches, end rule processing after executing the rule.
244 If this rule matches, start rule processing over from the very first
245 rule after executing this rule.
248 If this rule matches, refuse the request and send an access denied
252 This rule applies to GET (RRQ) requests only.
255 This rule applies to PUT (WRQ) requests only.
257 The following escape sequences are recognized as part of the
258 .IR "replacement pattern" :
261 The entire string matched by the
264 \fB\\1\fP to \fB\\9\fP
265 The strings matched by each of the first nine parenthesized
266 subexpressions, \\( ... \\), of the
271 The IP address of the requesting host, in dotted-quad notation
275 The IP address of the requesting host, in hexadecimal notation
281 \fB\\\fP\fIwhitespace\fP
287 If the mapping file is changed, you need to send
293 The use of TFTP services does not require an account or password on
294 the server system. Due to the lack of authentication information,
296 will allow only publicly readable files (o+r) to be accessed, unless the
298 option is specified. Files may be written only if they already exist
299 and are publicly writable, unless the
301 option is specified. Note that this extends the concept of ``public''
302 to include all users on all hosts that can be reached through the
303 network; this may not be appropriate on all systems, and its
304 implications should be considered before enabling TFTP service.
305 Typically, some kind of firewall or packet-filter solution should be
306 employed. If appropriately compiled (see the output of
311 database for access control information. This may be slow; sites
312 requiring maximum performance may want to compile without this option
313 and rely on firewalling or kernel-based packet filters instead.
315 The server should be set to run as the user with the lowest possible
316 privilege; please see the
318 flag. It is probably a good idea to set up a specific user account for
320 rather than letting it run as "nobody", to guard against privilege
321 leaks between applications.
323 Access to files can, and should, be restricted by invoking
325 with a list of directories by including pathnames as server program
326 arguments on the command line. In this case access is restricted to
327 files whole names are prefixed by one of the given directories. If
328 possible, it is recommended that the
330 flag is used to set up a chroot() environment for the server to run in
331 once a connection has been set up.
333 Finally, the filename remapping
335 flag) support can be used to provide a limited amount of additional
339 .IR "Requirements for Internet Hosts \- Application and Support" .
342 .IR "The TFTP Protocol (revision 2)" .
345 .IR "TFTP Option Extension" .
348 .IR "TFTP Blocksize Option" .
351 .IR "TFTP Timeout Interval and Transfer Size Options" .
355 is maintained by H. Peter Anvin <hpa@zytor.com>. It was derived from,
356 but has substantially diverged from, an OpenBSD source base, with
357 added patches by Markus Gutschke and Gero Kulhman.
362 .BR hosts_access (5),