Lines Matching full:host

3 hosts_access \- format of host access control files
6 based on client (host name/address, user name), and server (process
7 name, host name/address) patterns.  Examples are given at the end. The
17 a host requesting service. Network daemon process names are specified
57 of one or more host names, host addresses, patterns or wildcards (see
58 below) that will be matched against the client host name or address.
60 The more complex forms \fIdaemon@host\fR and \fIuser@host\fR are
72 A string that begins with a `.\' character. A host name is matched if
74 example, the pattern `.tue.nl\' matches the host name
77 A string that ends with a `.\' character. A host address is matched if
79 pattern `131.155.\' matches the address of (almost) every host on the
83 (formerly YP) netgroup name. A host name is matched if it is a host
88 `net/mask\' pair. A host address is matched if `net\' is equal to the
94 `[net]/prefixlen\' pair. A IPv6 host address is matched if
101 name. A host name or address is matched if it matches any host name
103 zero or more lines with zero or more host name or address patterns
105 a host name or address pattern can be used.
111 Matches any host whose name does not contain a dot character.
113 Matches any user whose name is unknown, and matches any host whose name
115 host names may be unavailable due to temporary name server problems. A
119 Matches any user whose name is known, and matches any host whose name
121 host names may be unavailable due to temporary name server problems.  A
125 Matches any host whose name does not match its address.  When tcpd is
157 The client (server) host address.
159 Client information: user@host, user@address, a host name, or just an
164 The client (server) host name or address, if the host name is
167 The client (server) host name (or "unknown" or "paranoid").
171 Server information: daemon@host, daemon@address, or just a daemon name,
196 The host_pattern obeys the same syntax rules as host names and
200 When the client host supports the RFC 931 protocol or one of its
203 information, when available, is logged together with the client host
211 client host.  In the case of rule-driven username lookups, the above
224 when the client host runs a suitable daemon; in all other cases the
247 service can be used to detect such and other host address spoofing
252 When the client host provides IDENT service, a negative IDENT lookup
253 result (the client matches `UNKNOWN@host') is strong evidence of a host
256 A positive IDENT lookup result (the client matches `KNOWN@host') is
274 The examples use host and domain names. They can be improved by
303 in the host name) and from members of the \fIsome_netgroup\fP
317 ALL: some.host.name, .some.domain
319 ALL EXCEPT in.fingerd: other.host.name, .other.domain
327 host. The result is mailed to the superuser.
348 The expansion of the %h (client host) and %d (service name) sequences
361 An error is reported when a syntax error is found in a host access
385 If a name server lookup times out, the host name will not be available
386 to the access control software, even though the host is registered.