Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I was wondering something. I am looking at deploying Snort/ACID on a few servers I have exposed to the WAN. Is it considered insecure to leave an interface that is connected to the WAN in promiscuous mode?
Not in of itself, but you are adding another piece of software that can (and has been) vulnerable to remote exploitation. An ideal way to run Snort is on a dedicated machine that is connected by an "ethertap" which is basically a one way ethernet cable (see snort docs for a howto). That way you're significantly reducing the likelihood of the IDS getting compromised.
You can actually install a bunch of Snort sensors that then send logs to a central analysis console that has /ACID/mySQL/Apache on it. Those apps really just make reviewing your logs more convienient. That may sound trivial, but on a fairly substantial network, Snort logs can can get really big in a short amount of time. Installing Snort on every machine is probably overkill. Putting it on a few well select machines that can observe all network traffic is probably a better solution.