Hi, Paul!
I don't know if we're talking about the same thing but here's how I did it
on our Solaris-boxes at work.
According to the installation instructions tcpd can be used as a
drop-in-replacement for all the daemons you want tcp-wrapper to protect. The
original daemons (in.ftpd, in.telnetd, etc. on a Solaris-box) are moved to
another directory (which tcp-wrapper has to know about; I put it in the
Makefile when I compiled tcpd). So when someone wants to connect via e.g.
telnet, inetd starts tcpd (renamed to in.telnetd) instead of the actual
telnet daemon. tcpd then does its works (checks IP-numbers, host.allow,
etc.) and if everything is OK it transfers the connection to the real telnet
daemon. In short, tcpd needs not be explicitly started by inetd. Maybe it's
different in Linux?
Hope this helps,
Olof
----- Original Message -----
From: "pawel kwas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 27, 2000 12:42 PM
Subject: [newbie] tcpd
> I need to use tcp wrappers. Do I need to put something in inetd.config to
> have it (tcpd) enabled at boot? I can't see any entry for it there.
>
> What is "auth" in inetd.config? What does it do? There is no manual page
> for it.
>
> Also when trying "netstat -ta" I get a table entries that show ports 6000
> and 1024 (are they open?).
> What's on those ports and how to close them?
>
> thanks
>
> Paul
>
>
>
____________NetZero Free Internet Access and Email_________
Download Now http://www.netzero.net/download/index.html
Request a CDROM 1-800-333-3633
___________________________________________________________
