Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
Currently, I am taking a Computer and Network Security course and have a question om my HW that asks for the six entries on the ENS /etc/hosts.deny file. We need to specifically address what each listed service does and what the system implications are for the entry in the /etc/hosts.deny file. At this time I have researched info on the file but am not finding such info. regarding to the entries. If anyone can direct me in the right direction for this info, I will greatly appreciate it.
The files /etc/hosts.allow and /etc/hosts.deny are used by a library named libwrap.so from the package tcp-wrappers (tcp_wrappers-libs-7.6-52.fc9.i386 in F9) and any "server" linked with it.
Common "servers" are sshd, rsyncd, cupsd, etc.
To check if a given server has support to tcpwrapper, check if it was linked to libwrap (ldd /usr/sbin/sshd | grep libwrap). If it is, than you can control its access using /etc/hosts.allow and /etc/hosts.deny files.
Think hosts.allow and hosts.deny as an access control on the application level, a kind of firewall for specific applications, not protocol/port as usual.
The files /etc/hosts.allow and /etc/hosts.deny are used by a library named libwrap.so from the package tcp-wrappers (tcp_wrappers-libs-7.6-52.fc9.i386 in F9) and any "server" linked with it.
Common "servers" are sshd, rsyncd, cupsd, etc.
To check if a given server has support to tcpwrapper, check if it was linked to libwrap (ldd /usr/sbin/sshd | grep libwrap). If it is, than you can control its access using /etc/hosts.allow and /etc/hosts.deny files.
Think hosts.allow and hosts.deny as an access control on the application level, a kind of firewall for specific applications, not protocol/port as usual.
Once we modify host.deny, do we have to restarrt any service to make it effective?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.