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.
No, su activities can't be audited back to an individual. You need a change control system. It doesn't need to be software, it can simply be a process. If you want an audit trail, enforce the use of sudo - prohibit su.
Last edited by macemoneta; 02-14-2007 at 11:43 PM.
If you want an audit trail, enforce the use of sudo - prohibit su.
If you want an audit trail that includes commands users execute (when they su to other accounts), force Sudo but also force using a logging shell wrapper like Rootsh or Sudosh. The main difference between the two AFAIK is that Sudosh has session playback capabilities. If you want to expand on that make the wrapper log to syslog and log to a remote syslog host.
You also may want to use a file integrity checker like Aide, Samhain or even tripwire to monitor changes. Top it off with a tool to monitor services for changes (like Monit). I have the most important configs under a revision system which makes it easy to check change info and revert back in case it gets fscked up.
Last edited by unSpawn; 02-15-2007 at 06:19 AM.
Reason: more is more.