[ Pobierz całość w formacie PDF ]
.HISTORYWritten by Rich $alz (rsalz@uunet.uu.net) for InterNetNews.SEE ALSOdbz(3z), expire(8), innd(8), news-recovery(8)hosts.nntp, hosts.nntp.nolimithosts.nntp, hosts.nntp.nolimit List of hosts that feed NNTP news.DESCRIPTIONThe file /news/lib/hosts.nntp is read by innd(8) to get the list of hosts that feed the local site Usenet news using the NNTPprotocol.The server reads this file at startup or when directed to by ctlinnd(8).When a hosts connects to the NNTP port ofthe system on which innd is running, the server will do a check to see if their Internet address is the same as one of the hostsnamed in this file.If the host is not mentioned, then innd will spawn an nnrpd(8) to process the connection, with theaccepted connection on standard input and standard output.Comments begin with a number sign (#) and continue through the end of the line.Blank lines and comments are alsoignored.All other lines should consist of two or three fields separated by a colon.The first field should be either an Internet address in dotted-quad format or an address that can be parsed bygethostbyname(3).If a host s entry has multiple addresses, all of them will be added to the access list.The second field, whichmay be blank, is the password the foreign host is required to use when first connecting.The third field, which may beomitted, is a list of newsgroups to which the host may post articles.This list is parsed as a newsfeeds(5) subscription list;groups not in the list are ignored.Because innd is usually started at system boot time, the local nameserver may not be fully operational when innd parses thisfile.As a work-around, a ctlinnd reload command can be performed after a delay of an hour or so.It is also possible toprovide both a host s name and its dotted-quad address in the file.For example:## FOO has a password, UUNET doesn t.## UUNET cannot post to local groups.## These are comment lines.news.foo.com:magicuunet.uu.net::!foo.*If the file contains passwords, it should not be world-readable.The file /news/lib/hosts.nntp.nolimit, if it exists, is readwhenever the hosts.nntp file is read.It has the same format, although only the first field is used.Any host mentioned in thisfile is not subject to the incoming connections limit specified by innd s  c flag.This can be used to allow local hosts or time-sensitive peers to connect regardless of the local conditions.hosts_access1133HISTORYWritten by Rich $alz (rsalz@uunet.uu.net) for InterNetNews.SEE ALSOctlinnd(8), innd(8), nnrpd(8)hosts_accesshosts_access Format of host access control files.DESCRIPTIONThis manual page describes a simple access control language that is based on client (hostname/address, username) and server(process name) patterns.Examples are given at the end.The impatient reader can skip to the  Examples section for a quickintroduction.In the following text, daemon is the process name of a network daemon process, and client is the name or address of a hostrequesting service.Network daemon process names are specified in the inetd configuration file.ACCESS CONTROL FILESThe access control software consults two files.The search stops at the first match:Access will be granted when a (daemon,client) pair matches an entry in the /etc/hosts.allow file.Otherwise, access will be denied when a (daemon,client) pair matches an entry in the /etc/hosts.deny file.Otherwise, access will be granted.A non-existing access control file is treated as if it were an empty file.Thus, access control can be turned off by providing noaccess control files.ACCESS CONTROL RULESEach access control file consists of zero or more lines of text.These lines are processed in order of appearance.The searchterminates when a match is found.A newline character is ignored when it is preceded by a backslash character.Blank lines or lines that begin with a # character are ignored.All other lines should satisfy the following format, things between [] being optional:daemon_list : client_list [ : shell_command ]daemon_list is a list of one or more daemon process names (argv[0] values) or wildcards.client_list is a list of one or more hostnames, host addresses, patterns, or wildcards that will be matched against the remotehostname or address.List elements should be separated by blanks or commas.With the exception of NIS (YP) netgroup lookups, all access control checks are case insensitive.PATTERNSThe access control language implements the following patterns:A string that begins with a.character: A client name or address is matched if its last components match the specifiedpattern.For example, the pattern.tue.nl matches the hostname wzv.win.tue.nl.A string that ends with a.character: A client name or address is matched if its first fields match the given string.Forexample, the pattern 131.155.matches the address of (almost) every host on the Eindhoven University network(131.155.x.x).Part V: File Formats1134A string that begins with a @ character is treated as a netgroup name: Netgroups are usually supported on systems with NIS(formerly YP) databases [ Pobierz całość w formacie PDF ]