-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write policy for starting/stopping/restarting auditd #194
Comments
@ykhodorkovskiy The toor user doesn't even have the DAC perms to do this in permissive. Should this user be able to start auditd or should this perm be reserved for a privileged role? |
This should only be done as root or a privileged role. From: Mike Palmiotto [mailto:[email protected]] [toor@localhost ~]$ getenforce && systemctl restart auditd.service @ykhodorkovskiyhttps://github.com/ykhodorkovskiy The toor user doesn't even have the DAC perms to do this in permissive. Should this user be able to start auditd or should this perm be reserved for a privileged role? — |
Ah, right. My bad. I was thinking toor_t was an unpriv user label. |
When I attempt to stop auditd with It appears that the proper usage is |
|
type=USER_AVC msg=audit(1438545469.052:1539): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc: denied { start } for auid=1000 uid=0 gid=0 path="/usr/lib/systemd/system/auditd.service" cmdline="systemctl restart auditd.service" scontext=toor_u:toor_r:toor_t:s0 tcontext=system_u:object_r:auditd_unit_file_t:s0 tclass=service exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
The text was updated successfully, but these errors were encountered: