1Upstream-Status: Backport 2 3diff -ruN tcp_wrappers_7.6.orig/hosts_access.5 tcp_wrappers_7.6/hosts_access.5 4--- tcp_wrappers_7.6.orig/hosts_access.5 1995-01-30 19:51:47.000000000 +0100 5+++ tcp_wrappers_7.6/hosts_access.5 2004-04-09 16:59:45.000000000 +0200 6@@ -173,7 +173,7 @@ 7 Patterns like these can be used when the machine has different internet 8 addresses with different internet hostnames. Service providers can use 9 this facility to offer FTP, GOPHER or WWW archives with internet names 10-that may even belong to different organizations. See also the `twist' 11+that may even belong to different organizations. See also the `twist\' 12 option in the hosts_options(5) document. Some systems (Solaris, 13 FreeBSD) can have more than one internet address on one physical 14 interface; with other systems you may have to resort to SLIP or PPP 15@@ -236,10 +236,10 @@ 16 Before accepting a client request, the wrappers can use the IDENT 17 service to find out that the client did not send the request at all. 18 When the client host provides IDENT service, a negative IDENT lookup 19-result (the client matches `UNKNOWN@host') is strong evidence of a host 20+result (the client matches `UNKNOWN@host\') is strong evidence of a host 21 spoofing attack. 22 .PP 23-A positive IDENT lookup result (the client matches `KNOWN@host') is 24+A positive IDENT lookup result (the client matches `KNOWN@host\') is 25 less trustworthy. It is possible for an intruder to spoof both the 26 client connection and the IDENT lookup, although doing so is much 27 harder than spoofing just a client connection. It may also be that 28diff -ruN tcp_wrappers_7.6.orig/hosts_options.5 tcp_wrappers_7.6/hosts_options.5 29--- tcp_wrappers_7.6.orig/hosts_options.5 1994-12-28 17:42:29.000000000 +0100 30+++ tcp_wrappers_7.6/hosts_options.5 2004-04-09 16:59:49.000000000 +0200 31@@ -124,7 +124,7 @@ 32 value is taken. 33 .SH MISCELLANEOUS 34 .IP "banners /some/directory" 35-Look for a file in `/some/directory' with the same name as the daemon 36+Look for a file in `/some/directory\' with the same name as the daemon 37 process (for example in.telnetd for the telnet service), and copy its 38 contents to the client. Newline characters are replaced by 39 carriage-return newline, and %<letter> sequences are expanded (see 40diff -ruN tcp_wrappers_7.6.orig/tcpdmatch.8 tcp_wrappers_7.6/tcpdmatch.8 41--- tcp_wrappers_7.6.orig/tcpdmatch.8 1996-02-11 17:01:36.000000000 +0100 42+++ tcp_wrappers_7.6/tcpdmatch.8 2004-04-09 17:00:49.000000000 +0200 43@@ -26,7 +26,7 @@ 44 A daemon process name. Typically, the last component of a daemon 45 executable pathname. 46 .IP client 47-A host name or network address, or one of the `unknown' or `paranoid' 48+A host name or network address, or one of the `unknown\' or `paranoid\' 49 wildcard patterns. 50 .sp 51 When a client host name is specified, \fItcpdmatch\fR gives a 52@@ -37,13 +37,13 @@ 53 .PP 54 Optional information specified with the \fIdaemon@server\fR form: 55 .IP server 56-A host name or network address, or one of the `unknown' or `paranoid' 57-wildcard patterns. The default server name is `unknown'. 58+A host name or network address, or one of the `unknown\' or `paranoid\' 59+wildcard patterns. The default server name is `unknown\'. 60 .PP 61 Optional information specified with the \fIuser@client\fR form: 62 .IP user 63 A client user identifier. Typically, a login name or a numeric userid. 64-The default user name is `unknown'. 65+The default user name is `unknown\'. 66 .SH OPTIONS 67 .IP -d 68 Examine \fIhosts.allow\fR and \fIhosts.deny\fR files in the current 69@@ -70,7 +70,7 @@ 70 .ti +5 71 tcpdmatch in.telnetd paranoid 72 .PP 73-On some systems, daemon names have no `in.' prefix, or \fItcpdmatch\fR 74+On some systems, daemon names have no `in.\' prefix, or \fItcpdmatch\fR 75 may need some help to locate the inetd configuration file. 76 .SH FILES 77 .PP 78