Hey people. I've removed tcp_wrappers and removed it from openssh and cups. Everything works fine. I've noticed Arch also removed it in 2011: https://www.archlinux.org/news/dropping-tcp_wrappers-support/ Since it makes more problems than it's worth, why have it? Why not remove it completely from core and leave it as an optional package? On 7.3.2014 04:14, Alan Mizrahi wrote:
James Mills <prologic@shortcircuit.net.au> escribió:
On Fri, Mar 7, 2014 at 8:51 AM, Wawrzek Niewodniczanski <main@wawrzek.name>wrote:
I know - it easy, but maybe not the most elegant. Anyway, I might probably end up doing it.
How exactly is a single one liner not elegant?
I find tcpwrappers not a very useful thing in general.
If you want/need firewalling -- you really should use/learn iptables/netfilter
As I said, do yourself a favor and use "ALL: ALL" and don't make things harder on yourself than you need to! :)
I agree with James, I often rebuild ports to remove tcpwrappers. I usually don't need it or use iptables instead.
Note that you can implement IP based ACLs in cupsd.conf, similar to apache.
Regards,
Alan _______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
_____________________________________________________ Postavite svoj mali oglas besplatno: http://oglasi.krstarica.com/