Results 1 to 2 of 2
I am trying to modify the behavior of tcp_wrappers on my system so that it will not perform reverse lookups on incoming requests for SSH. I am attempting to do ...
- 03-14-2009 #1Just Joined!
- Join Date
- Mar 2009
- Posts
- 1
TCP_Wrappers RPM Build
I am trying to modify the behavior of tcp_wrappers on my system so that it will not perform reverse lookups on incoming requests for SSH. I am attempting to do this by commenting out the relevant lines (below) in the makefile and then rebuilding the package:
PARANOID= -DPARANOID
HOSTNAME= -DALWAYS_HOSTNAME
I have downloaded the source RPMS and installed them to the appropriate directories (ie: /home/build/rpm/SOURCES, SPECS, etc... )
I then untar/unzip the source and modify the makefile in the source package and rezip and tar.
I then execute the following command and receive the following output:
[build@CentOS SPECS]$ rpmbuild -bb tcp_wrappers.spec
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.55540
+ umask 022
+ cd /home/build/rpm/BUILD
+ cd /home/build/rpm/BUILD
+ rm -rf tcp_wrappers_7.6
+ /bin/gzip -dc /home/build/rpm/SOURCES/tcp_wrappers_7.6.tar.gz
+ tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd tcp_wrappers_7.6
++ /usr/bin/id -u
+ '[' 501 = 0 ']'
++ /usr/bin/id -u
+ '[' 501 = 0 ']'
+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ echo 'Patch #0 (tcpw7.2-config.patch):'
Patch #0 (tcpw7.2-config.patch):
+ patch -p1 -b --suffix .config -s
1 out of 10 hunks FAILED -- saving rejects to file Makefile.rej
error: Bad exit status from /var/tmp/rpm-tmp.55540 (%prep)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.55540 (%prep)
[build@CentOS SPECS]$
Below is the excerpt from the make and patch file:
################################################## ##
# Optional: dealing with host name/address conflicts
#
# By default, the software tries to protect against hosts that claim to
# have someone elses host name. This is relevant for network services
# whose authentication depends on host names, such as rsh and rlogin.
#
# With paranoid mode on, connections will be rejected when the host name
# does not match the host address. Connections will also be rejected when
# the host name is available but cannot be verified.
#
# Comment out the following definition if you want more control over such
# requests. When paranoid mode is off and a host name double check fails,
# the client can be matched with the PARANOID access control pattern.
#
# Paranoid mode implies hostname lookup. In order to disable hostname
# lookups altogether, see the next section.
#PARANOID= -DPARANOID
########################################
# Optional: turning off hostname lookups
#
# By default, the software always attempts to look up the client
# hostname. With selective hostname lookups, the client hostname
# lookup is postponed until the name is required by an access control
# rule or by a %letter expansion.
#
# In order to perform selective hostname lookups, disable paranoid
# mode (see previous section) and comment out the following definition.
#HOSTNAME= -DALWAYS_HOSTNAME
#############################################
Patch Excerpt
##################################################
# Optional: Always attempt remote username lookups
@@ -520,7 +521,7 @@
# still do selective username lookups as documented in the hosts_access.5
# and hosts_options.5 manual pages (`nroff -man' format).
#
-#AUTH = -DALWAYS_RFC931
+AUTH = #-DALWAYS_RFC931
#
# The default username lookup timeout is 10 seconds. This may not be long
# enough for slow hosts or networks, but is enough to irritate PC users.
@@ -579,7 +580,7 @@
# Paranoid mode implies hostname lookup. In order to disable hostname
# lookups altogether, see the next section.
-PARANOID= -DPARANOID
+PARANOID= #-DPARANOID
########################################
# Optional: turning off hostname lookups
@@ -592,7 +593,7 @@
# In order to perform selective hostname lookups, disable paranoid
# mode (see previous section) and comment out the following definition.
-HOSTNAME= -DALWAYS_HOSTNAME
+HOSTNAME= #-DALWAYS_HOSTNAME
#############################################
Does anybody know where I am going wrong or a different way to produce a similar result?
- 01-08-2010 #2Just Joined!
- Join Date
- Dec 2009
- Location
- Atlanta
- Posts
- 5
I really don't see any errors but, what linux are you using?


Reply With Quote