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'm new here and am fairly new to linux and even more of a linux security newbie.
I'm trying to set up a system at work with some initial auditing options. I've got Red Hat Linux 9.0 running on a single processor system. I've so far found solutions to almost all my auditing needs, which mostly include the monitoring for attempted access to security relevent files/directories. I'm using snare 0.9.6 for this.
But I'm still missing the auditing for a certain event. I'd like to audit when someone attempts to change the system date via the date program, weather it be successful or unsuccessful. I obviously can't just watch the date program because users are allowed to run it, they just can't feed it a spring to change the date. I don't know of any file that get's touched or checked when the date program is ran in order to change the date. Is there maybe a logging feature in the system I can turn on to track this, or is there maybe a library that is accessed when the date program attempts to change the date that isn't access when it just returns the date? Either enabling a system option or watching a file for attempted access should be easy to implement, I just don't know where to look.
But I'm still missing the auditing for a certain event. I'd like to audit when someone attempts to change the system date via the date program, weather it be successful or unsuccessful.
In any case you'll have to be root to be able to change the time (using "date" is rather crude too)...
If you're watching syscalls, it'll be settimeofday. That's what "date -s" and ntpd use.
If you're out to deny people access to change system time (after you set it properly on boot) use "lcap" to remove the CAP_SYS_TIME capability. Note this will deny root running ntpd, will make a flakey system if the BIOS clock drifts and can not be undone except for a reboot.