Re: [newbie] security: tcpd daemon with /etc/xinetd.d/

2001-12-03 Thread Kathy Montgomery

My installation of xinetd (from the downloadable CD images) came with tcpd
capabilities already compiled in, so that I did not have to add the tcpd
information to my xinetd.conf file.

When I make changes to the host.allow and host.deny files, xinetd restricts
access accordingly, without any reference to tcpd in the configuration file.
Have you tried this?  (I welcome corrections if I'm off base...)

- Kathy

tek1 wrote:

 in my linux: the complete reference book on p.559, it explain that to use
 tcp wrappers (for monitoring connections and controlling access), we need
 to put tcpd in front of the service name in the inetd.conf file.

 however, mandrake uses the xinetd.conf file, which doesn't list the
 services.  instead, it includes the dir /etc/xinetd.d/, which are the
 equivalent of listing the services in xinetd.conf.  but how do we wrap the
 services in /etc/xinetd.d/ in a tcpd wrapper?

 thanks...


--
For God has not given us a spirit of fear, but of power and of love and of a
sound mind. - 2 Timothy 1:7





Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [newbie] security: tcpd daemon with /etc/xinetd.d/

2001-12-03 Thread civileme

On Monday 03 December 2001 09:24 am, Kathy Montgomery wrote:
 My installation of xinetd (from the downloadable CD images) came with tcpd
 capabilities already compiled in, so that I did not have to add the tcpd
 information to my xinetd.conf file.

 When I make changes to the host.allow and host.deny files, xinetd restricts
 access accordingly, without any reference to tcpd in the configuration
 file. Have you tried this?  (I welcome corrections if I'm off base...)

 - Kathy

 tek1 wrote:
  in my linux: the complete reference book on p.559, it explain that to
  use tcp wrappers (for monitoring connections and controlling access), we
  need to put tcpd in front of the service name in the inetd.conf file.
 
  however, mandrake uses the xinetd.conf file, which doesn't list the
  services.  instead, it includes the dir /etc/xinetd.d/, which are the
  equivalent of listing the services in xinetd.conf.  but how do we wrap
  the services in /etc/xinetd.d/ in a tcpd wrapper?
 
  thanks...

You are correct.  There is no need for a lot of what used to be recommended.  
 When we still used inetd, the tcp_wrappers were installed and configured by 
default and it was ard to get rid of them even then, but that is no longer 
necessary with xinetd.

Civileme



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



[newbie] security: tcpd daemon with /etc/xinetd.d/

2001-12-01 Thread tek1

in my linux: the complete reference book on p.559, it explain that to use 
tcp wrappers (for monitoring connections and controlling access), we need 
to put tcpd in front of the service name in the inetd.conf file.

however, mandrake uses the xinetd.conf file, which doesn't list the 
services.  instead, it includes the dir /etc/xinetd.d/, which are the 
equivalent of listing the services in xinetd.conf.  but how do we wrap the 
services in /etc/xinetd.d/ in a tcpd wrapper?

thanks... 




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com