Well, xinetd basically has tcpd built in - and you can specify times of day
when things can be accessed, max number of processes to fork at a time, and
so on. The downside is that most of the tools for installing things know
the inetd format but not the xinetd format, so that's a bit of a downer, but
the xinetd.conf format is pretty easy to learn.
Whether or not that constitutes major advantages is very much in the eye of
the beholder...but I happen to like it.
Martin Jackson
===================
mhjacks@nwa.quik.com
----- Original Message -----
From: Peter Münster
On Tue, 6 Mar 2001, Joop Boonen wrote:
service. So if you set-up telnet or pop3 you can restrict the addresses that can use it. This is not possible with inetd that you have to use a portwrapper or a firewall to accomplish this. I meant client addresses.
Are you sure? I read something else a while ago on this list. You should do perhaps a "man inetd"...
What i see in man inetd is that you can specify a local address, so if an interface ahs more than one ip address , or when you have multiple interfaces. But every person can still use the specified service when it's connected to the right ip address/port. Correct me when i'm wrong.
I don't know, I've never read the manual of inetd... But it seems, that I didn't understand that *major advantage*. Is it just the functionality of tcpd? Peter
-- Peter Münster http://notrix.net/pm-vcard
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com