ftpusers(5) [netbsd man page]
FTPUSERS(5) BSD File Formats Manual FTPUSERS(5) NAME
ftpusers, ftpchroot -- ftpd(8) access control file DESCRIPTION
The ftpusers file provides user access control for ftpd(8) by defining which users may login. If the ftpusers file does not exist, all users are denied access. A ``'' is the escape character; it can be used to escape the meaning of the comment character, or if it is the last character on a line, extends a configuration directive across multiple lines. A ``#'' is the comment character, and all characters from it to the end of line are ignored (unless it is escaped with the escape character). The syntax of each line is: userglob[:groupglob][@host] [directive [class]] These elements are: userglob matched against the user name, using fnmatch(3) glob matching (e.g, 'f*'). groupglob matched against all the groups that the user is a member of, using fnmatch(3) glob matching (e.g, '*src'). host either a CIDR address (refer to inet_net_pton(3)) to match against the remote address (e.g, '1.2.3.4/24'), or an fnmatch(3) glob to match against the remote hostname (e.g, '*.NetBSD.org'). directive If ``allow'' or ``yes'' the user is allowed access. If ``deny'' or ``no'', or directive is not given, the user is denied access. class defines the class to use in ftpd.conf(5). If class is not given, it defaults to one of the following: chroot If there is a match in /etc/ftpchroot for the user. guest If the user name is ``anonymous'' or 'ftp'. real If neither of the above is true. No further comparisons are attempted after the first successful match. If no match is found, the user is granted access. This syntax is backward-compatible with the old syntax. If a user requests a guest login, the ftpd(8) server checks to see that both ``anonymous'' and ``ftp'' have access, so if you deny all users by default, you will need to add both ``anonymous allow'' and ``ftp allow'' to /etc/ftpusers in order to allow guest logins. /etc/ftpchroot The file /etc/ftpchroot is used to determine which users will have their session's root directory changed (using chroot(2)), either to the directory specified in the ftpd.conf(5) chroot directive (if set), or to the home directory of the user. If the file does not exist, the root directory change is not performed. The syntax is similar to ftpusers, except that the class argument is ignored. If there's a positive match, the session's root directory is changed. No further comparisons are attempted after the first successful match. This syntax is backward-compatible with the old syntax. FILES
/etc/ftpchroot List of normal users who should have their ftp session's root directory changed by using chroot(2). /etc/ftpusers This file. /usr/share/examples/ftpd/ftpusers A sample ftpusers file. SEE ALSO
fnmatch(3), inet_net_pton(3), ftpd.conf(5), ftpd(8) BSD
July 17, 2000 BSD
Check Out this Related Man Page
ftpusers(4) File Formats ftpusers(4) NAME
ftpusers - file listing users to be disallowed ftp login privileges SYNOPSIS
/etc/ftpd/ftpusers DESCRIPTION
The ftpusers file lists users for whom ftp login privileges are disallowed. Each ftpuser entry is a single line of the form: name where name is the user's login name. The FTP Server, in.ftpd(1M), reads the ftpusers file. If the login name of the user matches one of the entries listed, it rejects the login attempt. The ftpusers file has the following default configuration entries: root daemon bin sys adm lp uccp nuucp smmsp listen nobody noaccess nobody4 These entries match the default instantiated entries from passwd(4). The list of default entries typically contains the superuser root and other administrative and system application identities. The root entry is included in the ftpusers file as a security measure since the default policy is to disallow remote logins for this iden- tity. This policy is also set in the default value of the CONSOLE entry in the /etc/default/login file. See login(1). If you allow root login privileges by deleting the root entry in ftpusers, you should also modify the security policy in /etc/default/login to reflect the site security policy for remote login access by root. Other default entries are administrative identities that are typically assumed by system applications but never used for local or remote login, for example sys and nobody. Since these entries do not have a valid password field instantiated in shadow(4), no login can be per- formed. If a site adds similar administrative or system application identities in passwd(4) and shadow(4), for example, majordomo, the site should consider including them in the ftpusers file for a consistent security policy. Lines that begin with # are treated as comment lines and are ignored. FILES
/etc/ftpd/ftpusers A file that lists users for whom ftp login privileges are disallowed. /etc/ftpusers See /etc/ftpd/ftpusers. This file is deprecated, although its use is still supported. /etc/default/login /etc/passwd password file /etc/shadow shadow password file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWftpr | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ The interface stability for /etc/ftpd/ftpusers is Volatile. The interface stability for /etc/ftpusers is (Obsolete). SEE ALSO
login(1), in.ftpd(1M), ftpaccess(4), ftphosts(4), passwd(4), shadow(4), attributes(5), environ(5) SunOS 5.11 1 May 2003 ftpusers(4)