gtpc1m4pTransmission Control Protocol/Internet Protocol

Directives for the TFTP Configuration File

Each line of the TFTP configuration file must contain an EBCDIC string starting in column 1 and ending with a line-feed character (X'0A'), which is the format of a normal text file from UNIX.

Note:
A DOS-based editor ends lines with both the carriage-return and line-feed characters (X'0D0A'). The TFTP server turns this character combination into just the line-feed character; therefore, files from either DOS or UNIX are acceptable.

The allow and deny directives control which directories and subdirectories are accessible to TFTP clients. If there are allow and deny directives for the same directory, access is denied.

#
Specifies a comment line. Use comment lines sparingly because like all other lines in the configuration file, they are processed.

AUTH
Specifies the file access permissions that are set for all files written by the TFTP server on behalf of TFTP clients using a TFTP write request. The access permissions must be three octal characters (0-7); for example, AUTH=444.

If an AUTH directive is not specified or is not specified correctly in the TFTP configuration file, access permissions are set to 444 octal. This allows owner, group, and other read access.

The access permissions for a particular file can subsequently be modified by the ZFILE chmod command. See TPF Operations for more information about the ZFILE chmod command.

LOG
Specifies the name of a file in the file system where the TFTP server records status lines. If the specified file does not already exist in the TPF file system, it is created. The file name must be a fully qualified path name that begins with a slash (/).

If a LOG directive is not specified in the TFTP configuration file, the /tmp/tftp.log file is used for logging.

allow
Specifies a directory where files can be accessed (read or write). All subdirectories are also accessible unless specifically prohibited with a deny directive. You must specify the path file name; that is, the path name must start with a slash (/).

deny
Specifies a directory where files cannot be accessed. All subdirectories are also not accessible unless there is an allow directive for the subdirectory. You must specify the full path name; that is, the path name must start with a slash (/).

The following is an example of allow and deny directives:

    allow:/a
    deny:/a/b

The /a/filename.type and /a/c/filename.type files are accessible because the allow directive grants access and there is no deny directive that prevents access.

The /filename.type and /e/filename.type files are not accessible because they are not explicitly granted access by the allow directive. The /a/b/filename.type file is not accessible because access is prevented by the deny directive.