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.
What can be done to prevent unauthorized hosts from getting access to my network? In other words what would prevent someone from plugging into my hub and getting an ip? I could give ips to only certain hardware addresses but couldn't someone set a static on within an acceptable range?
In samba i could set hosts allow, but that just limits access based on ip's = hostname in lmhosts; correct? I think a machine with the an acceptable ip would get access even if the netbios name did not match.
ideas? RH7.2, Samba with windows xp and 98 clients
Short answer - given time and opportunity, bugger all.
But..... you can make it difficult.
Replace the hub(s) with a layer 3 switch (es) and read up on ACLs.
Restrict each (switch) port to a specific MAC address and block unused ports (so to spoof a MAC address, they have to pull something off the network - your users _may_ notice when someone nicks their connection.)
You could set the ACLs so that the MAC address can't reconnect to the port within a certain period of time (1/2 hr ?), but this is flaky if J Random Luser reboots his machine a lot.
Unfortunately, in XP and 2000 you can change the MAC address on your machine to whatever you want, so an ACL based around MAC addresses is breakable, but not too bad.
If your server is running as a DHCP server as well, then u could creat rules that only those MAC are accpeted by the DHCP server and all others will not get a addr. To get these addr and MAC addr try using the cmd arp -a
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.