Feature changed by: Christoph Thiel (cthiel1) Feature #120053, revision 35 Title: Restrict Services By Interface in Inetd YaST module openSUSE-10.3: Rejected by Thorsten Kukuk (kukuk) reject date: 2007-11-21 10:53:32 reject reason: Rewrite postponed to 11.1 Priority Requester: Desirable Projectmanager: Desirable openSUSE-11.0: Rejected by Jiri Srain (jsrain) reject date: 2006-09-06 16:49:59 reject reason: Affected module will be rewritten for 10.3. Priority Requester: Desirable openSUSE-11.1: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-06-27 14:32:29 reject reason: Out of resources, postponing. Priority Requester: Desirable - openSUSE-11.2: Evaluation + openSUSE-11.2: Rejected by Christoph Thiel (cthiel1) + reject date: 2009-05-26 20:39:11 + reject reason: Out of resources for 11.2. Existing functionallity in + yast2 firewall should be sufficient. Priority Requester: Desirable Requested by: Martin Vidner (mvidner) Description: Restrict services by interface, e.g. write a generic tcpwrappers library for other yast modules. References: Bug 49800 (https://bugzilla.novell.com/show_bug.cgi?id=49800) Discussion: #1: Lukas Ocilka (locilka) (2006-07-21 08:52:01) This probably depends on feature #100110: Possible Merge With Inetd Editor #2: Jiri Srain (jsrain) (2006-09-06 16:49:22) (reply to #1) Yes, doesn't make much sense if the module(s) will be rewritten... #3: Lukas Ocilka (locilka) (2006-10-23 17:22:49) Martin, please, add more suggestions how to restrict these services if you have some idea. Thanks. #4: Martin Vidner (mvidner) (2006-10-23 17:33:54) Technically: man xinetd.conf: bind Allows a service to be bound to a specific interface on the machine. This means you can have a telnet server listening on a local, secured interface, and not on the external interface. Or one port on one interface can do something, while the same port on a different interface can do something completely different. Syntax: bind = (ip address of interface). -- openSUSE Feature: https://features.opensuse.org/120053