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.
My usernames and dates for events generated by auditd into the audit.log file look weired. I can not make out the date and user who provoked the event. All the other logs look good. Any clue how to fix?
Timestamp has standard UNIX epoch time stamp format. "Users" are of the .*UID variety. From now on* make it your default to be specific in your questions. Saying "weird" is NOT an objective description. And also make it a habit to voluntarily provide *exact* details, configs, log excerpts and whatnot to support your questions.
Below is a sample of what my auditd logs look like. Is there a way to make the output of the logs more transparent to the vieweer; in other words the user action, dates and times are more consisitent with the other logs (SYSTEM for example) where it is apparent without a great deal of diffiuctly to determine who did what and when.
True, but it also greps for "^type=SYSCALL.*success=no" since not everybody reads system call numbers (I know I don't). The CRED/USER lines are kind of selfexplanatory IMHO. I mean all that's left to expand are IDs, nothing else is obfuscated, right?
True, but it also greps for "^type=SYSCALL.*success=no" since not everybody reads system call numbers (I know I don't). The CRED/USER lines are kind of selfexplanatory IMHO. I mean all that's left to expand are IDs, nothing else is obfuscated, right?
I changed this line:
tac /var/log/audit/audit.log | grep -m 30 "^type=SYSCALL.*success=no" | tac | while read LINE; do
to be:
tac /var/log/audit/audit.log |grep -v cron |grep -v login | tac | while read LINE; do
This is useful if you are just watching a few certin files, and want more detailed info than what AIDE can do.
Thanks for posting, however that won't work (you'd see a lot of "ENOFILE" mistranslations) because not every audit message consist of the same amount and similar value elements:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.