| Main index | Section 8 | 日本語 | Options |
The use of
tftp(1)
does not require an account or password on the remote system.
Due to the lack of authentication information,
tftpd
will allow only publicly readable files to be
accessed.
Files containing the string
"/../"
or starting with
"../"
are not allowed.
Files may be written only if they already exist (unless the
Access to files may be restricted by invoking tftpd with a list of directories by including up to 20 pathnames as server program arguments in inetd.conf(5). In this case access is restricted to files whose names are prefixed by the one of the given directories. The given directories are also treated as a search path for relative filename requests.
The
The options are:
| | |
|
By default,
tftpd
expects an initial message to be available on its input socket.
If no data is available, the server exits immediately.
If
| |
| | |
|
Changes the default root directory of a connecting host via
chroot(2)
based on the connecting IP address.
This prevents multiple clients from writing to the same file at the same time.
If the directory does not exist, the client connection is refused.
The
| |
| | |
|
Operates the same as
| |
| | |
|
Use this
strftime(3)
compatible format string for the creation of the suffix if
| |
| | |
|
Enables debug output.
If
value
is not specified, then the debug level is increased by one
for each instance of
If
value
is specified, then the debug level is set to
value.
The debug level is a bitmask implemented in
src/libexec/tftpd/tftp-utils.h.
Valid values are 0 (DEBUG_NONE), 1 (DEBUG_PACKETS), 2, (DEBUG_SIMPLE),
4 (DEBUG_OPTIONS), and 8 (DEBUG_ACCESS). Multiple debug values can be combined
in the bitmask by logically OR'ing the values. For example, specifying
| |
| | |
| Log all requests using syslog(3) with the facility of LOG_FTP. Note: Logging of LOG_FTP messages must also be enabled in the syslog configuration file, syslog.conf(5). | |
| | |
| Suppress negative acknowledgement of requests for nonexistent relative filenames. | |
| | |
| Disable support for RFC2347 style TFTP Options. | |
| | |
| Cause tftpd to change its root directory to directory. After doing that but before accepting commands, tftpd will switch credentials to an unprivileged user. | |
| | |
| If tftpd runs chrooted, the option allows write requests according to generic file permissions, skipping requirement for files to be publicly writable. The option is ignored for non-chrooted run. | |
| | |
|
Switch credentials to
user
(default
"nobody")
when the
| |
| | |
| Set the umask for newly created files. The default is 022 ( S_IWGRP | S_IWOTH). | |
| | |
|
Allow write requests to create new files.
By default
tftpd
requires that the file specified in a write request exist.
Note that this only works in directories writable by the user
specified with
| |
| | |
|
As
| |
The following RFC's are supported:
RFC 1350: The TFTP Protocol (Revision 2),
RFC 2347: TFTP Option Extension,
RFC 2348: TFTP Blocksize Option,
RFC 2349: TFTP Timeout Interval and Transfer Size Options,
RFC 7440: TFTP Windowsize Option,
The non-standard rollover and blksize2 TFTP options are mentioned here: http://www.compuphase.com/tftp.htm
Extending TFTP,
Support for Timeout Interval and Transfer Size Options (RFC2349) was introduced in FreeBSD 5.0, support for the TFTP Blocksize Option (RFC2348) and the blksize2 option was introduced in FreeBSD 7.4 .
Edwin Groothuis <edwin@FreeBSD.org> performed a major rewrite of the tftpd and tftp(1) code to support RFC2348.
Support for the windowsize option (RFC7440) was introduced in FreeBSD 13.0 .
Many tftp clients will not transfer files over 16,776,703 octets (32767 blocks), as they incorrectly count the block number using a signed rather than unsigned 16-bit integer.
| TFTPD (8) | November 3, 2024 |
| Main index | Section 8 | 日本語 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | Computer science would have progressed much further and faster if all of the time and effort that has been spent maintaining and nurturing Unix had been spent on a sounder operating system. | ” |
| — The Unix Haters' handbook | ||