Re: [PATCH] audit: add task history record
On August 26, 2023 2:38:55 AM Tetsuo Handa
<penguin-kernel(a)I-love.SAKURA.ne.jp> wrote:
On 2023/08/25 12:36, Paul Moore wrote:
>> It is unfortunate that you continue ignoring the
> >> How can auditd generate logs that are not triggered
via syscalls?
> >> line. I know how to configure syscall rules using
"-S" option. But I do
>> not know how to configure non syscall rules (such as process creation via
>> kthread_create(), process termination due to tty hangup or OOM killer).
> At this point you've exhausted my goodwill so I would
suggest simply reading
> the audit code, manages, and experimenting with a running system to understand
> how things work, especially for non-syscall records.
Are we on the same page that non-syscall records include process creation via
kthread_create() and process termination via send_sig() ?
I'm not confident that we are in agreement on many of the issues in this
thread, some of that is likely due to disagreements in what functionality
is worthwhile, but I believe some of that is due to misunderstandings. I'm
not going to merge the patch you posted at the start of this thread, but as
I've mentioned *several* times now, if you find a kernel code path that is
missing an audit logging call submit a patch with an explanation of why the
audit call is needed and we can discuss it.
My initial thinking is that we do not need, or want, an audit call in
kthread_create(). I'm less sure about send_sig(), and as my network access
is limited at the moment I don't have the ability to look into it further
right now. If you feel we do need an additional audit call, create a patch,
test it, write a good commit description explaining why it is necessary and
we can review it.
--
paul-moore.com