Linux - Security This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
11-13-2001, 10:00 PM
|
#1
|
LQ Newbie
Registered: Nov 2001
Distribution: Red Hat 6.2
Posts: 17
Rep:
|
Hosts.allow file
Is there a way I can put a wildcard in this file? For example if I want to accept any connections from say "all.me.net.nz" Is this how I should enter it :
ALL:ALL@ME.NET.NZ:ALLOW
IF not then what is the syntax?
|
|
|
11-14-2001, 02:12 PM
|
#2
|
Member
Registered: Aug 2001
Location: CT, USA
Distribution: Mandriva 2008
Posts: 105
Rep:
|
I've not used this much, but believe you can accomplish what you want by specifying the IP address
ALL: 123.45.67.890
Adding something like :ALLOW would be redundant since you're editing the HOSTS.ALLOW file; that's if it even worked....
|
|
|
11-14-2001, 02:48 PM
|
#3
|
Moderator
Registered: May 2001
Posts: 29,415
|
Id like to add you can use hosts/netmasks and separate them with comma's as well for more fine-grained control:
example0: 110.1.0.0/16
example1: 110.1.24.0/24, 110.1.25.0/24, 254.1.2.132/32
or:
example2: ALL EXCEPT 127.0.0.1, 200.210.0.0/16
As a final note Id like to say this doesn't work automagically, the app has to be compiled with TCP-Wrappers support (like ./configure --with-libwrap) to take advantage of this.
|
|
|
11-16-2001, 10:49 AM
|
#4
|
Member
Registered: Apr 2001
Location: London
Posts: 408
Rep:
|
Yes wildcards will work in TCP wrappers using the follow implementation.
The access control language implements the following patterns:
A string that begins with a `.´ character.
A host name is matched if the last components of its name match the specified pattern.
For example, the pattern `.tue.nl´ matches the host name `wzv.win.tue.nl´.
A string that ends with a `.´ character.
A host address is matched if its first numeric fields match the given string.
For example, the pattern `131.155.´ matches the address of (almost) every host on the Eindhoven University network (131.155.x.x).
Check out man hosts.deny for more info..
/Raz
|
|
|
All times are GMT -5. The time now is 02:29 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|