$Id$	       =======================================Starting in version 0.27, tftp-hpa has the option of a "use Unixpermissions" mode.  In this mode, tftpd can access any file accessibleby the tftpd effective user, specified via the -u option.  This meansthat files no longer need to be set to o+r or o+w.If file creation is enabled (via the -c option), the -p option alsochanges the default umask from 0 (anyone can read or write) to"unchanged" (inherited from the calling process.)  The -U option canbe used to override the default umask; this is recommended.The sanest setup, from a security standpoint, for tftpd to run in isprobably the following:1. Create a separate "tftpd" user and group only used for tftpd;2. Have all your boot files in a single directory tree (usually called    /tftpboot).3. Specify "-p -u tftpd -s /tftpboot" on the tftpd command line; if   you want clients to be able to create files use   "-p -c -U 002 -u tftpd -s /tftpboot" (replace 002 with whatever   umask is appropriate for your setup.)	       =======================================Starting in version 0.17, tftp-hpa operates in genuine "wait" mode,which means that an in.tftpd process hangs around for some time afterthe last service request has arrived.  This speeds up servicing asubsequent request, which apparently has been a problem in the past,resulting in "request storms" as the client keeps retrying, resultingin multiple connections on the server which the client has alreadyabandoned.This also means that spawning tftp via tcpd is useless (in fact, thisindirection seems to be part of the reason for these "requeststorms.")  Instead, tftp-hpa supports calling the tcpwrapper librarydirectly.  Thus, if your /etc/inetd.conf looks like this (all on oneline):tftp	dgram	udp	wait	root	/usr/sbin/tcpd/usr/sbin/in.tftpd -s /tftpboot -r blksize... it's better to change to ...tftp	dgram	udp	wait	root	/usr/sbin/in.tftpdin.tftpd -s /tftpboot -r blksizeYou should make sure that you are using "wait" option in tftpd; youalso need to have tftpd spawned as root in order for chroot (-s) towork.  tftpd automatically drops privilege and changes user ID to"nobody" by default; the appropriate user ID for tftpd can bespecified with the -u option (e.g. "-u tftpuser").If you are running a busy boot server, I would suggest to instead usekernel-based firewalling rules, and to compile tftpd withouttcpwrapper support, in order to provide significantly betterperformance.  To do so, specify the --without-tcpwrappers option toconfigure when compiling; see the INSTALL.tftp file for more information.