[PATCH ghak96] audit: set cwd in audit context for file-related LSM audit records
paul at paul-moore.com
Fri Apr 17 22:21:59 UTC 2020
On Thu, Apr 9, 2020 at 5:51 PM Richard Guy Briggs <rgb at redhat.com> wrote:
> On 2020-04-02 12:31, Vladis Dronov wrote:
> > Hello, Casey, all,
> > ----- Original Message -----
> > > From: "Casey Schaufler" <casey at schaufler-ca.com>
> > > Subject: Re: [PATCH ghak96] audit: set cwd in audit context for file-related LSM audit records
> > >
> > > On 4/2/2020 7:13 AM, Vladis Dronov wrote:
> > > > Set a current working directory in an audit context for the following
> > > > record
> > > > types in dump_common_audit_data(): LSM_AUDIT_DATA_PATH,
> > > > LSM_AUDIT_DATA_FILE,
> > > > LSM_AUDIT_DATA_IOCTL_OP, LSM_AUDIT_DATA_DENTRY, LSM_AUDIT_DATA_INODE so a
> > > > separate CWD record is emitted later.
> > > >
> > > > Link: https://github.com/linux-audit/audit-kernel/issues/96
> > >
> > > I don't have a problem with the patch, but it sure would be nice
> > > if you explained why these events "could use a CWD record".
> > (adding Richard Guy Briggs <rgb at redhat.com> which I should have been done earlier)
> > I would agree, adding "cwd=" field in the LSM record itself is simpler to me.
> We already have a CWD record to record this information. It usually
> accompanies an AUDIT_PATH record, but the intent is that it accompanies
> any event that has filesystem pathnames in path= or name= fields in
> records to help understand the command's context relative to the
Yes, I think the right thing to do here is simply generate a CWD
record in these cases.
More information about the Linux-security-module-archive