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.
rhel 5.7 fully updated,
i havent tried this yet, searched LQ but nothing specific.
can i EXCEPT the wildcard keyword ALL
ALL: ALL EXCEPT RFC1918, RFC1918, RFC1918
this would make my life easy since i am trying out denyhosts service. my hosts.allow would be empty. i would like to do it this way to outright deny anything that is not internal IP, then allow denyhosts to write (stack) deny entries for any brute forcing of ssh that might happen from internal IP. and yes, i know about iptables.
Last edited by Linux_Kidd; 10-07-2011 at 07:17 PM.
if i place rfc's in hosts.allow then denyhosts adding entries to hosts.deny would be completely useless. using a combo of sshd config, pam config, and the use of denyhosts gets me the layers and functionality i want w/o extra stuff.
anyone know the answer to my question about the syntax?
nope, doesnt help. i know what all the texts say. it doesnt explain if EXCEPT will apply to the match all "ALL" wildcard keyword. all the man pages give examples of `list_1 EXCEPT list_2', is "ALL" wildcard considered a list?
MOSTLY OPEN
Here, access is granted by default; only explicitly specified hosts are refused service.
The default policy (access granted) makes the allow file redundant so that it can be omitted. The explicitly non-authorized hosts are listed in the deny file. For example:
/etc/hosts.deny: ALL: some.host.name, .some.domain
ALL EXCEPT in.fingerd: other.host.name, .other.domain
The first rule denies some hosts and domains all services; the second rule still permits finger requests from other hosts and domains.
thnx. yes, that example does shows an "ALL EXCEPT" but its on the service side. i will assume the parsing rules carry over to the client_list section (no reason to think it doesnt). i cannot find and example matching mine so i'll just give it a try next week. thnx.
update:
ALL: ALL EXCEPT works as expected.
with a combo of tcpd, pam, and denyhosts i have a flexible configuration that contains access/auth controls at different levels.
Last edited by Linux_Kidd; 10-11-2011 at 03:47 PM.
Reason: tested my setup
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.