From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Reboots and audit.rules
Date: Thu, 30 Mar 2017 11:33:27 -0400 [thread overview]
Message-ID: <1514563.jQEK1XCEs1@x2> (raw)
In-Reply-To: <CAJdJdQnYiNEBhME4zK69LDjA75A57Eh4z=P8Cc6SWHGjbQ+gVA@mail.gmail.com>
On Thursday, March 30, 2017 8:17:05 AM EDT warron.french wrote:
> Steve, is there anyway that you know of both as the author of the Red Hat
> Audit software, and also an employee of Red Hat that would allow someone to
> review the audit logs and determine one of the following 2 possibilities:
We have specification around most things these days. This is the document about
system lifecycle events:
https://github.com/linux-audit/audit-documentation/wiki/SPEC-System-Lifecycle-Events
According to it, the event you are looking for is SYSTEM_SHUTDOWN. The reason
for shutdown is not required.
> 1. If the machine was rebooted through software; such as;
>
> - poweroff,
> - shutdown,
> - init, etc.. etc..
You could place watches on these if you really wanting this information.
> 2. Or a person pressed the power button on the front of the machine.
There is also hibernate and pulling the power cord.
-Steve
> I ran into this problem in the workplace last year, and this feature would
> be helpful, but I don't know if it is already offered covering the
> power-button depression; versus the command execution.
>
> I understand that with a power-button depression there is no way of
> capturing the/a userid; perhaps a hidden default account of "power-button"
> would suffice?
>
>
> Thank you,
> --------------------------
> Warron French
prev parent reply other threads:[~2017-03-30 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 12:17 Reboots and audit.rules warron.french
2017-03-30 14:36 ` Ryan Sawhill
[not found] ` <CAJdJdQnqeRWwhHWj79FY3Wp8BabKc0xb+ue8knEmzmOjkV1oXg@mail.gmail.com>
2017-03-30 22:34 ` Ryan Sawhill
2017-03-30 15:33 ` Steve Grubb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1514563.jQEK1XCEs1@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox