Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
I'm confused over what "NAMES" to use to deny NFS services to clents.
I only do Ad-hoc wireless NFS sharing between two computers & I do
not go thru my internet itpable firewall.
My /etc/hosts.deny looks like this & is based on "rpcinfo" display names:
All:192.168. EXCEPT 192.168.1.1 192.168.1.2
Fedora systemctl output:
nfs-idmap.service loaded active running NFSv4 ID-name mapping daemon
nfs-lock.service loaded active running NFS file locking service.
nfs-mountd.service loaded active running NFS Mount Daemon
nfs-rquotad.service loaded active running NFS Remote Quota Server
nfs-server.service loaded active exited NFS Server
rpcbind.service loaded active running RPC bind service
rpcbind.socket loaded active listening RPCbind Server Activation Socket
Why are you being so specific? Are there services 192.168.1.1 and 192.168.1.2 shouldn't access? If not, why not just use the following in /etc/hosts.allow?
host.deny:
All:192.168. EXCEPT 192.168.1.1 192.168.1.2 ..This entry is probably all that is needed as it should cover all the "daemon-processes" listed below & more
It is my understanding that just listing a host in the host.allow file doesn't stop other hosts from connecting. You have to exclude them or deny them by access to daemon processes running on your network by specific entries in the host.deny file.
My host.deny file may be a bit redundant but I wanted to list the specific daemon-processes my wireless net was using. Just using "All" for the daemon-process denies access to all tcp-wrapper libary linked processes. I wanted to know what processes are being blocked.
The big problem for me was finding out what "names" to use in the host.deny file. I spent a lot of time reading the manual pages & searching the web before I decided on the names shown above. I hope I have it right.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.