Re: Why is syscall auditing on with no rules?
On Mon, Feb 3, 2014 at 6:49 AM, Steve Grubb <sgrubb(a)redhat.com> wrote:
On Saturday, February 01, 2014 06:51:56 PM Andy Lutomirski wrote:
> On Sat, Feb 1, 2014 at 6:32 PM, Andy Lutomirski <luto(a)amacapital.net> wrote:
> > On a stock Fedora installation:
> >
> > $ sudo auditctl -l
> > No rules
What rules would you want? The audit package ships with several which affects
performance to varying degrees. The default one affects it the least. If you
don't want auditing, don't install the audit package.
Actually, 'task,never' is lower overhead on 3.13, but I'm fine with
"No rules". However...
> > How hard would it be to arrange for TIF_SYSCALL_AUDIT to be
cleared
> > when there are no syscall rules?
This only gets set if auditing is enabled. What if in the future someone loads
rules? For example, what if you reload audit rules? The first thing that
happens is it clears any previous rules. If we did what you suggested, then
any process that runs between the time the rules were deleted and a rule gets
loaded will never be auditable. We can't have that. Sometimes admins stop the
audit daemon to do some looking around. Usually audit rules are cleared when
its stopped. Once again you have a window where processes will become
inauditable.
We take the point of view that if you want auditing and all that it brings
with it, this will be setup by the audit daemon. If you want no auditing and
no performance hit, simply don't install it or disable it from starting and
all will be fine.
I actually do want auditing -- I need it if I want to see AVC denials.
But I don't want syscall auditing, nor do most people, which is
entirely consistent with the default rules.
It's permissible to set and clear TIF_SYSCALL_AUDIT from a different
thread. Given that changing the list of syscall audit rules is
probably *much* rarer than calling a syscall and that
TIF_SYSCALL_AUDIT appears to more than double total syscall latency on
Sandy Bridge (and it quite possible even worse on newer hardware), it
seems to me that a much better solution would be to dynamically turn
TIF_SYSCALL_AUDIT on and off.
I wouldn't hesitate to implement this, except that I'm a bit scared of
the code. (e.g. why is audit_context in task_struct still there even
if syscsall auditing is configured out. What happens if a task enters
a syscall w/ TIF_SYSCALL_AUDIT clear and returns with it set or vice
versa?)
I'd go even farther and allow auditing to be globally turned on after
processes are created (removing the need for audit=1 or whatever), but
that would require a lot more familiarity with the code.
--Andy