From: Paul Moore <paul@paul-moore.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: audit@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>,
linux-audit@redhat.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] audit: add task history record
Date: Thu, 24 Aug 2023 10:26:06 -0400 [thread overview]
Message-ID: <CAHC9VhRTVsoMWhP1+j7RcUqy2EiV=Z7W_00h55PE-WezzLg=Ew@mail.gmail.com> (raw)
In-Reply-To: <e56ed3a6-9d82-a181-bbc7-e322ea47cb98@I-love.SAKURA.ne.jp>
On Thu, Aug 24, 2023 at 9:47 AM Tetsuo Handa
<penguin-kernel@i-love.sakura.ne.jp> wrote:
> On 2023/08/24 22:39, Tetsuo Handa wrote:
> >>> (1) Catch _all_ process creations (both via fork()/clone() system calls and
> >>> kthread_create() from the kernel), and duplicate the history upon process
> >>> creation.
> >>
> >> Create an audit filter rule to record the syscalls you are interested
> >> in logging.
> >
> > I can't interpret what you are talking about. Please show me using command line.
>
> I'm not interested in logging the syscalls just for maintaining process history
> information.
That's unfortunate because I'm not interested in merging your patch
when we already have an audit log which can be used to trace process
history information.
--
paul-moore.com
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2023-08-24 14:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 10:58 [PATCH] audit: add task history record Tetsuo Handa
2023-08-11 17:50 ` Richard Guy Briggs
2023-08-12 10:08 ` Tetsuo Handa
2023-08-15 18:44 ` Paul Moore
2023-08-16 10:10 ` Tetsuo Handa
2023-08-16 13:53 ` Paul Moore
2023-08-18 10:29 ` Tetsuo Handa
2023-08-18 14:59 ` Paul Moore
2023-08-19 7:09 ` Tetsuo Handa
2023-08-21 16:04 ` Serge E. Hallyn
2023-08-21 22:23 ` Tetsuo Handa
2023-08-21 16:35 ` Paul Moore
2023-08-23 14:18 ` Tetsuo Handa
2023-08-23 14:48 ` Paul Moore
2023-08-24 13:21 ` Tetsuo Handa
2023-08-24 13:30 ` Paul Moore
2023-08-24 13:39 ` Tetsuo Handa
2023-08-24 13:47 ` Tetsuo Handa
2023-08-24 14:26 ` Paul Moore [this message]
2023-08-24 22:24 ` Tetsuo Handa
2023-08-25 3:36 ` Paul Moore
2023-08-26 6:38 ` Tetsuo Handa
2023-08-26 14:47 ` Paul Moore
2023-08-24 14:24 ` Paul Moore
2023-08-24 15:55 ` Steve Grubb
2023-08-24 17:02 ` Paul Moore
2023-08-22 16:29 ` Steve Grubb
2023-08-22 17:58 ` Paul Moore
2023-08-21 17:29 ` Serge Hallyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHC9VhRTVsoMWhP1+j7RcUqy2EiV=Z7W_00h55PE-WezzLg=Ew@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=audit@vger.kernel.org \
--cc=linux-audit@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).