Executable permissions
Is there a reason that the audit tools that take a file name paramater (-if) are not executable by non-root users? This prevents their use by an admin to do analysis of saved audit logs with an unprivileged user login.
Thanks - Karl
Quoted 2 lines · Karl MacMillan
Is there a reason that the audit tools that take a file name paramater (-if) are not executable by non-root users?
Current tools do not.
[root src]# grep getuid *.c
auditctl.c: if (getuid() != 0) {
auditctl.c: if (getuid() != 0) {Must be root to send netlink
auditd.c: if (getuid() != 0) {
Must be root to read netlink
autrace.c: if (getuid() != 0) {
Must be root to write to netlink.
-Steve
Quoted 14 lines · Steve Grubb
Quoted 2 lines · Karl MacMillan
Is there a reason that the audit tools that take a file name paramater (-if) are not executable by non-root users?
Current tools do not.
[root src]# grep getuid *.c
auditctl.c: if (getuid() != 0) { auditctl.c: if (getuid() != 0) {Must be root to send netlink
Quoted 7 lines
auditd.c: if (getuid()!= 0) {Must be root to read netlink
autrace.c: if (getuid()!= 0) {Must be root to write to netlink.
I think Karl is talking about the mode bits. The audit tools are 750, owned by root,root, on my system, so not executable by non-root users.
-- ljk
Quoted 6 lines · Steve Grubb
Quoted 2 lines · Karl MacMillan
Is there a reason that the audit tools that take a file name paramater (-if) are not executable by non-root users?
Current tools do not.
[root@localhost ~]# ls -l /sbin/au*
-rwxr-x--- 1 root root 3080 Dec 1 11:37 /sbin/audispd* -rwxr-x--- 1 root root 88216 Dec 1 11:37 /sbin/auditctl* -rwxr-x--- 1 root root 96068 Dec 1 11:37 /sbin/auditd* -rwxr-x--- 1 root root 102864 Dec 1 11:37 /sbin/aureport* -rwxr-x--- 1 root root 115420 Dec 1 11:37 /sbin/ausearch* -rwxr-x--- 1 root root 68816 Dec 1 11:37 /sbin/autrace*
[root@localhost ~]# rpm -qa | grep audit
audit-libs-1.3-3.fc7
audit-1.3-3.fc7
audit-libs-python-1.3-3.fc7
audit-libs-devel-1.3-3.fc7
It's not the code, but rather the default permissions on the executables. So this might just be a packaging problem.
Thanks - Karl
Quoted 1 line · Karl MacMillan
So this might just be a packaging problem.
Yeah, I think I can open it for those two programs.
-Steve