in.tftpd(8) [debian man page]
TFTPD(8) BSD System Manager's Manual TFTPD(8) NAME
tftpd -- DARPA Trivial File Transfer Protocol server SYNOPSIS
tftpd [-n] [-s] [directory ...] DESCRIPTION
Tftpd is a server which supports the DARPA Trivial File Transfer Protocol. The TFTP server operates at the port indicated in the 'tftp' ser- vice description; see services(5). The server is normally started by inetd(8). 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 may be written only if they already exist and are publicly writable. Note that this extends the concept of ``public'' to include all users on all hosts that can be reached through the network; this may not be appropriate on all systems, and its implications should be considered before enabling tftp service. The server should have the user ID with the lowest possible privilege. Access to files may be controlled by invoking tftpd with a list of directories by including pathnames as server program arguments in /etc/inetd.conf. In this case access is restricted to files whose names are prefixed by the one of the given directories. If no directories are supplied the default is /tftpboot. To give out access to the whole filesystem, should this be desired for some reason, supply / as an argument. Unfortunately, on multi-homed systems, it is impossible for tftpd to determine the address on which a packet was received. As a result, tftpd uses two different mechanisms to guess the best source address to use for replies. If the socket that inetd(8) passed to tftpd is bound to a particular address, tftpd uses that address for replies. Otherwise, tftpd uses ``UDP connect'' to let the kernel choose the reply address based on the destination of the replies and the routing tables. This means that most setups will work transparently, while in cases where the reply address must be fixed, the virtual hosting feature of inetd(8) can be used to ensure that replies go out from the correct address. These considerations are important, because most tftp clients will reject reply packets that appear to come from an unexpected address. The options are: -n Suppresses negative acknowledgement of requests for nonexistent relative filenames. -s All absolute filenames are treated as if they were preceded by the first directory argument, or /tftpboot if there is none. SEE ALSO
tftp(1), inetd(8) HISTORY
The tftpd command appeared in 4.2BSD. Linux NetKit (0.17) July 29, 2000 Linux NetKit (0.17)
Check Out this Related Man Page
in.tftpd(1M) in.tftpd(1M) NAME
in.tftpd, tftpd - Internet Trivial File Transfer Protocol server SYNOPSIS
in.tftpd [-s] [homedir] tftpd is a server that supports the Internet Trivial File Transfer Protocol (TFTP). Before responding to a request, the server attempts to change its current directory to homedir; the default directory is /tftpboot. The use of tftp does not require an account or password on the remote system. Due to the lack of authentication information, in.tftpd will allow only publicly readable files to be accessed. Files may be written only if they already exist and are publicly writable. Note that this extends the concept of "public" to include all users on all hosts that can be reached through the network. This may not be appropriate on all systems, and its implications should be considered before enabling this service. in.tftpd runs with the user ID and group ID set to [GU]ID_NOBODY under the assumption that no files exist with that owner or group. How- ever, nothing checks this assumption or enforces this restriction. -d Debug. When specified it sets the SO_DEBUG socket option. -s Secure. When specified, the directory change to homedir must succeed. The daemon also changes its root directory to homedir. The in.tftpd server is IPv6-enabled. See ip6(7P). See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWtftp | +-----------------------------+-----------------------------+ svcs(1), tftp(1), inetadm(1M), inetd(1M), svcadm(1M), netconfig(4), attributes(5), smf(5), ip6(7P) Malkin, G. and Harkin, A. RFC 2347, TFTP Option Extension. The Internet Society. May 1998 Malkin, G. and Harkin, A. RFC 2348, TFTP Blocksize Option. The Internet Society. May 1998 Malkin, G. and Harkin, A. RFC 2349, TFTP Timeout Interval and Transfer Size Options. The Internet Society. May 1998 Sollins, K.R. RFC 1350, The TFTP Protocol (Revision 2). Network Working Group. July 1992. The tftpd server only acknowledges the transfer size option that is sent with a read request when the octet transfer mode is specified. The in.tftpd.1m service is managed by the service management facility, smf(5), under the service identifier: svc:/network/tftp/udp6:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). Responsibil- ity for initiating and restarting this service is delegated to inetd(1M). Use inetadm(1M) to make configuration changes and to view config- uration information for this service. The service's status can be queried using the svcs(1) command. Unlike most smf(5) services, a manifest for the tftp service is not included in the system. To create one and enable this service, the administrator should: 1. Edit /etc/inet/inetd.conf and uncomment the tftp entry. 2. Run /usr/sbin/inetconv. After you run inetconv, the svc:/network/tftp/udp6:default service is created and enabled. 8 Mar 2005 in.tftpd(1M)