[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: tcpd with xinetd



On Sat, 4 Jul 1998, Matus fantomas Uhlar wrote:

> -> Why would you want to do this? Xinetd already has access control based on
> -> ip address, host name and time of day. What features of tcpd are you
> -> missing in xinetd?
> 
> many features; you probaby don't know all features of tcpd and some limits
> of xinetd when you're asking this (sorry).
> 
> 1. tcpd has all configuration in one or two files and can be used together
> with many programs

xinetd has all configuration in one file, with tcpd and inetd you have at
least two config files. I don't know which is best.

> 2. for example you cannot allow/deny .domain.tld in xinetd

True. xinetd can do something with network names mentioned in
/etc/networks, though I have never figured out the exact format for this
file.

> 3. you can selectively allow/deny domains subdomains and hosts with tcpd
> 
> all:deny
> domain:allow
> subdomain.domain:deny
> host.subdomain.domain:allow
> 
> etc.

This can be useful in some cases, though probably not many people will
need a setup like this.

> 4. read manual page for hosts_options
> 
> of course some features would be redunant but i still think joining tcpd and
> xinetd would be great

You are right, I did't know all these features. I'd think the best way to
incorporate them into xinetd is to merge the programs into a better
xinetd. Unfortunately, I don't have the skills to help with such a
project. But you have my moral support. :)

Remco


--  
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: