From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Steve Grubb <sgrubb@redhat.com>,
linux-security-module <linux-security-module@vger.kernel.org>,
audit@vger.kernel.org, linux-audit@redhat.com
Subject: Re: [PATCH v2] TaskTracker : Simplified thread information tracker.
Date: Mon, 7 Aug 2023 23:24:51 +0900 [thread overview]
Message-ID: <ab7b4099-d238-e791-6dc2-25be5952798c@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <2029076.tdWV9SEqCh@x2>
On 2023/08/07 7:01, Steve Grubb wrote:
> This is where the problem begins. We like to have normalized audit records.
> Meaning that a type of event defines the fields it contains. In this case
> subject would be a process label. and there is already a precedent for what
> fields belong in a syscall record.
What is the definition of "a process label"? SELinux / Smack / AppArmor are using
security_secid_to_secctx() hook for providing string data for the subj= field.
I don't think that they are restricting characters that can be included.
Then, what is wrong with returning subset of ASCII printable characters from
tt_secid_to_secctx() ?
static int selinux_secid_to_secctx(u32 secid, char **secdata, u32 *seclen)
{
return security_sid_to_context(secid,
secdata, seclen);
}
static int smack_secid_to_secctx(u32 secid, char **secdata, u32 *seclen)
{
struct smack_known *skp = smack_from_secid(secid);
if (secdata)
*secdata = skp->smk_known;
*seclen = strlen(skp->smk_known);
return 0;
}
int apparmor_secid_to_secctx(u32 secid, char **secdata, u32 *seclen)
{
/* TODO: cache secctx and ref count so we don't have to recreate */
struct aa_label *label = aa_secid_to_label(secid);
int flags = FLAG_VIEW_SUBNS | FLAG_HIDDEN_UNCONFINED | FLAG_ABS_ROOT;
int len;
AA_BUG(!seclen);
if (!label)
return -EINVAL;
if (apparmor_display_secid_mode)
flags |= FLAG_SHOW_MODE;
if (secdata)
len = aa_label_asxprint(secdata, root_ns, label,
flags, GFP_ATOMIC);
else
len = aa_label_snxprint(NULL, 0, root_ns, label, flags);
if (len < 0)
return -ENOMEM;
*seclen = len;
return 0;
}
>
> What I would suggest is to make a separate record: AUDIT_PROC_TREE that
> describes process tree from the one killed up to the last known parent. This
> way you can define your own format and SYSCALL can stay as everyone expects it
> to look. In the EXECVE audit record, there is a precedent of using agv[0]=xx
> argv[1]=xx argv[2]=yy and so on. If you want to make these generally
> parsable without special knowledge of the record format, I'd suggest
> something like it.
Yes, https://lkml.kernel.org/r/201501202220.DJJ34834.OLJOHFMQOFtSVF@I-love.SAKURA.ne.jp
used AUDIT_PROCHISTORY instead of LSM hooks, but that thread died there.
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2023-08-07 14:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 13:04 [PATCH v2] TaskTracker : Simplified thread information tracker Tetsuo Handa
2023-08-06 22:01 ` Steve Grubb
2023-08-07 14:24 ` Tetsuo Handa [this message]
2023-08-07 17:25 ` Casey Schaufler
2023-08-07 18:54 ` Steve Grubb
2023-08-08 10:25 ` Tetsuo Handa
2023-08-07 18:53 ` Paul Moore
2023-08-07 19:03 ` Steve Grubb
2023-08-07 20:13 ` Paul Moore
2023-08-08 10:07 ` Tetsuo Handa
2023-08-08 14:38 ` Paul Moore
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=ab7b4099-d238-e791-6dc2-25be5952798c@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=audit@vger.kernel.org \
--cc=linux-audit@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=sgrubb@redhat.com \
/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).