Jim Cheetham
2011-09-08 23:11:48 UTC
I've been thinking about giving a different distro time on my desktop
recently, and having heard positive things about ArchLinux (as well as
seeing good-quality documentation show up in random google searches) I
thought I'd have a look.
I haven't got past their front-page, to be honest. I don't quite know
how to evaluate this news item ;-
https://www.archlinux.org/news/dropping-tcp_wrappers-support/
"""
News: Dropping tcp_wrappers support
2011-07-16 - Dan McGee
tcp_wrappers support is being dropped from all packages and the
package removed from [core]. This is due to upstream not having
released a new version since April 1997. Additionally, newer daemons
and applications are inconsistent in their support for libwrap,
leading to confusion as to whether an application supports the
library.
If you currently use /etc/hosts.allow or /etc/hosts.deny for security
or logging purposes, you will need to adjust accordingly and use
another tool such as iptables, or other firewall helper programs.
Additionally, the denyhosts package will be dropped as it depends on
tcp_wrappers to enforce the banned hosts list. A useful alternative is
fail2ban.
"""
I don't quite understand their stated reasons -- they're dropping the
code because it's stable? Or is there a long stack of bugs with
libwrap that are unaddressed by upstream? Or because it isn't popular
enough?
Can someone help me decide whether ArchLinux are rational or not over
this issue?
-jim
_______________________________________________
NZLUG mailing list ***@linux.net.nz
http://www.linux.net.nz/cgi-bin/mailman/listinfo/nzlug
recently, and having heard positive things about ArchLinux (as well as
seeing good-quality documentation show up in random google searches) I
thought I'd have a look.
I haven't got past their front-page, to be honest. I don't quite know
how to evaluate this news item ;-
https://www.archlinux.org/news/dropping-tcp_wrappers-support/
"""
News: Dropping tcp_wrappers support
2011-07-16 - Dan McGee
tcp_wrappers support is being dropped from all packages and the
package removed from [core]. This is due to upstream not having
released a new version since April 1997. Additionally, newer daemons
and applications are inconsistent in their support for libwrap,
leading to confusion as to whether an application supports the
library.
If you currently use /etc/hosts.allow or /etc/hosts.deny for security
or logging purposes, you will need to adjust accordingly and use
another tool such as iptables, or other firewall helper programs.
Additionally, the denyhosts package will be dropped as it depends on
tcp_wrappers to enforce the banned hosts list. A useful alternative is
fail2ban.
"""
I don't quite understand their stated reasons -- they're dropping the
code because it's stable? Or is there a long stack of bugs with
libwrap that are unaddressed by upstream? Or because it isn't popular
enough?
Can someone help me decide whether ArchLinux are rational or not over
this issue?
-jim
_______________________________________________
NZLUG mailing list ***@linux.net.nz
http://www.linux.net.nz/cgi-bin/mailman/listinfo/nzlug