diff options
author | Eric Paris <eparis@redhat.com> | 2012-01-03 14:23:05 -0500 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2012-01-17 16:16:55 -0500 |
commit | 16c174bd95cb07c9d0ad3fcd8c70f9cea7214c9d (patch) | |
tree | 3264c533da56cc81988331fd0d3f42f3d2ba3183 /kernel/rcutiny.c | |
parent | 3035c51e8ac0512686ceb9f2bd1d13bdc6e4fb29 (diff) | |
download | linux-stable-16c174bd95cb07c9d0ad3fcd8c70f9cea7214c9d.tar.gz linux-stable-16c174bd95cb07c9d0ad3fcd8c70f9cea7214c9d.tar.bz2 linux-stable-16c174bd95cb07c9d0ad3fcd8c70f9cea7214c9d.zip |
audit: check current inode and containing object when filtering on major and minor
The audit system has the ability to filter on the major and minor number of
the device containing the inode being operated upon. Lets say that
/dev/sda1 has major,minor 8,1 and that we mount /dev/sda1 on /boot. Now lets
say we add a watch with a filter on 8,1. If we proceed to open an inode
inside /boot, such as /vboot/vmlinuz, we will match the major,minor filter.
Lets instead assume that one were to use a tool like debugfs and were to
open /dev/sda1 directly and to modify it's contents. We might hope that
this would also be logged, but it isn't. The rules will check the
major,minor of the device containing /dev/sda1. In other words the rule
would match on the major/minor of the tmpfs mounted at /dev.
I believe these rules should trigger on either device. The man page is
devoid of useful information about the intended semantics. It only seems
logical that if you want to know everything that happened on a major,minor
that would include things that happened to the device itself...
Signed-off-by: Eric Paris <eparis@redhat.com>
Diffstat (limited to 'kernel/rcutiny.c')
0 files changed, 0 insertions, 0 deletions