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.
Distribution: Mandrake 9.1, 10.1, SuSE 8.1 pro, 10.1, Red Hat 8.0/9.0
Did we just get hacked?
I was looking at our Web Server log files last night and I saw what I think is a hack attempt. I am not sure, but it seems like the person thought this was a Windows box and I see that they tried to get a hold of cmd.exe, thus a Windows config file which I assume was meant for not so friendly purposes...can anybody give me a hint if this is indeed a hack attack???
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Well, you don't really monitor "ports" per se, but rather applications (after all, it's not good hitting a port if nothing exploitable is listening on it for traffic). You should review all your application logs regularly for suspicious behavior. There are several scripts out there to pick out odd log entries and bring them to your attention. Logwatch is one of them that comes to mind, but there are many others.
For monitoring all network traffic you'll want a Network Intrusion Detection System. Snort is by far the most popular of these. Nearly every Linux and BSD distribution has a pre-built package with Snort. You can also check www.snort.org.
if you run an IDS for any period of time you'll learn that your machine will be scanned/tested for these IIS exploits nearly every day, its very common, just make sure you dont run it or if you do, patch it to buggery, patch patch patch patch and you'll be ok, usually its just oportunistic script kiddies scanning large blocks