Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Missing tcpdmatch and tcpdchk in RedHat 7.1

Status
Not open for further replies.

clickguy

Programmer
Nov 18, 2001
7
US
Hi.

I recently did a "complete" Red Hat 7.1 install and notice that I don't have tcpdmatch or tcpdchk, even though when I do a rpm - q tcp_wrappers it shows tcp_wrappers-7.6-18 as being installed. I don't even have the man pages for those commands. tcpd seems to be installed, though.

Any ideas on what went wrong and how I can get tcpdmatch and tcpdchk installed?

Thanks!
 
Hi,







Well, according to the 'spec' file in the source rpm, they were removed because they referred to /etc/inetd.conf and redhat has been using xinetd instead of inetd for some time now. The following is the relevant bit of the spec file :







# XXX remove utilities that expect /etc/inetd.conf (#16059).



#install -m755 tcpdchk ${RPM_BUILD_ROOT}%{_sbindir}



#install -m755 tcpdmatch ${RPM_BUILD_ROOT}%{_sbindir}



rm -f ${RPM_BUILD_ROOT}%{_mandir}/man8/tcpdmatch.*



rm -f ${RPM_BUILD_ROOT}%{_mandir}/man8/tcpdchk.*






You could download the source from the author's site --> ftp://ftp.porcupine.org/pub/security/ and compile yourself but you'd come up against the same problem.






Hope this helps











 
Appreciate the info. That explains a lot -- at least I know I didn't louse up my install. :)

So of course my follow-up question is: Does anyone know of a replacement for tcpdchk and tcpdmatch? Is there an "xtcpdchk" or "xtcpdmatch" that looks at the xinetd files?

I'm trying to validate my hosts.allow and hosts.deny files and I've read that these two programs are used for that purpose.

TIA!
 
Hi,





Although conceptually the same, xinetd is quite a bit different in application to inetd and uses directives within the config files like :





only_from = 192.168.1.0/24





So, hosts.allow & hosts.deny (part of tcp wrappers) are not necessarily used in the same way. However, if xinetd has been compiled with libwrap then it first checks those two files and then, if allowed, checks its own permissions. I don't know for sure but i would guess that redhat xinetd is compiled to recognise tcp wrappers - might check the source rpm later...





See this article for a better idea of xinetd -->




Regards
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top