On Sun, Sep 09, 2001 at 06:31:57PM -0400, hpknight wrote:
> It depends on the process that is binding the port. If you're using
> xinetd you can specify which interface to bind the port on. If the
> program/daemon doesn't allow you to specify interfaces, then you're stuck
> .. unless you want to do some fancy stuff with ipchains/iptables to
> redirect ports, or hack up the daemon.
inetd also has this feature (not very well documented).
use service@ip in inetd.conf in order to use that feature.
xinetd is nicer, anyway :-)
First binding then firewalling is a bad idea, someone might be able to
access that service via spoofing or other dirty tricks...
MfG/Regards, Alexander
--
Alexander Reelsen http://joker.rhwd.de
[EMAIL PROTECTED] GnuPG: pub 1024D/F0D7313C sub 2048g/6AA2EDDB
[EMAIL PROTECTED] 7D44 F4E3 1993 FDDF 552E 7C88 EE9C CBD1 F0D7 313C
Securing Debian: http://joker.rhwd.de/doc/Securing-Debian-HOWTO
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
