You are not logged in.
- Topics: Active | Unanswered
#1 2012-07-01 17:32:45
- MoonSwan
- Member
- From: Great White North
- Registered: 2008-01-23
- Posts: 881
[Solved] hosts file is NOT deprecated -- but hosts.deny/allow? [YES]
I want to use the hosts file to map all my local networked machines just for convenience sake but I remember reading this somehwere:
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.
I understand why tcpwrappers and the hosts.deny/allow files have been tossed out but does this also mean the hosts file is obsolete? If it is then what do I use?
Thank you. 
Last edited by MoonSwan (2012-08-02 17:42:56)
Offline
#2 2012-07-01 18:03:51
- satanselbow
- Member
- Registered: 2011-06-15
- Posts: 538
Re: [Solved] hosts file is NOT deprecated -- but hosts.deny/allow? [YES]
Sounds unlikely - the hosts file is a universal networking fundamental whereas hosts.allow/deny was sketchily supported at best 
Offline
#3 2012-07-01 21:50:00
- ataraxia
- Member
- From: Pittsburgh
- Registered: 2007-05-06
- Posts: 1,553
Re: [Solved] hosts file is NOT deprecated -- but hosts.deny/allow? [YES]
No, hosts.deny and hosts.allow were used by tcp_wrappers, as described, but /etc/hosts is read by glibc (libnss in particular), which is a much different and more fundamental system component. It's not going anywhere.
Offline
#4 2012-07-01 23:14:01
- fukawi2
- Ex-Administratorino
- From: .vic.au
- Registered: 2007-09-28
- Posts: 6,237
- Website
Re: [Solved] hosts file is NOT deprecated -- but hosts.deny/allow? [YES]
No, hosts.deny and hosts.allow were used by tcp_wrappers, as described, but /etc/hosts is read by glibc (libnss in particular), which is a much different and more fundamental system component. It's not going anywhere.
This.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline