From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Maupertuis Philippe <philippe.maupertuis@worldline.com>
Subject: Re: Audit of physical users
Date: Tue, 03 Sep 2013 17:04:10 -0400 [thread overview]
Message-ID: <2217910.2QUQCy6Liz@x2> (raw)
In-Reply-To: <A35547AE65CDA84F93D4012BDFB5D5553DA7C28D29@FRVDX100.fr01.awl.atosorigin.net>
On Monday, September 02, 2013 02:49:28 PM Maupertuis Philippe wrote:
> I have a requirement to trace the activity of the physical users on Redhat
> 5/6 systems. I spent the last week sifting through the archive to find
> that the question was asked time and again. The basic rule is easy but the
> hitch is when an administrator restarts a service. Unfortunately, it seems
> there is no solution until systemd is used to start daemon instead of
> service.
Depending on how ambitious you are, you can write a little C program that
opens /proc/self/loginuid and writes -1, then close, and execve the intended
program. You will still have a sessionid that is not -1, but you have a
solution. At the same time, it also means that admins could use the same tool
to bypass audit rules. So, you'd probably want to think about it a bit.
> The only useful thing I found was in this old post from 2007
> http://www.redhat.com/archives/linux-audit/2007-February/msg00071.html to
> reset the auid. I would like to know if it can be used with the current
> version of auditd.
Probably, but you don't really need to link against libaudit. If you looked at
the source to audit_setloginuid(), its just open /proc/self/loginuid and
writing to it.
> If yes, I will probably give it a try with a fixed
> dedicated auid to clearly state that the auid was changed. Do I need to
> install something besides audit and audit-libs ?
> Is there any special need, for compiling this program ?
I'd simplify.
-Steve
prev parent reply other threads:[~2013-09-03 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 12:49 Audit of physical users Maupertuis Philippe
2013-09-03 21:04 ` 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=2217910.2QUQCy6Liz@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=philippe.maupertuis@worldline.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.