From: Steve Grubb <sgrubb@redhat.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: linux-audit@redhat.com
Subject: Re: Is auditing ftruncate useful?
Date: Fri, 06 Mar 2020 11:59:50 -0500 [thread overview]
Message-ID: <2633528.kLtZZfLx0Y@x2> (raw)
In-Reply-To: <bfd41bc4-7251-ef19-4ab8-6336f5eaf3f1@schaufler-ca.com>
On Monday, February 10, 2020 6:29:22 PM EST Casey Schaufler wrote:
> On 2/10/2020 3:05 PM, Orion Poplawski wrote:
> > On 2/10/20 3:54 PM, Paul Moore wrote:
> > So, this is all reasonable. But why do I get this with fchown which also
> > takes a file descriptor?
> > ...
> >
> > It's this disparity between fchown and ftruncate that caught my
> > attention.
>
> fchown changes the security state (mode bits) of the file,
> whereas ftruncate changes the content of the file. The former
> is clearly security relevant, the latter is not.
Well, security relevant or not, the requirement that the rule meets is
located here:
https://www.niap-ccevs.org/MMO/PP/-442-/#fau
File and object events (Successful and unsuccessful attempts to create,
access, delete, modify, modify permissions),
Since they separate modify and modify permissions, they clearly want changes
to content. Now, in the real world is that necessary? Maybe only in super
important scenarios where you have to know any change to anything.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2020-03-06 17:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 23:27 Is auditing ftruncate useful? Orion Poplawski
2020-02-06 15:37 ` Lenny Bruzenak
2020-02-06 18:12 ` Orion Poplawski
2020-02-06 18:33 ` Lenny Bruzenak
2020-02-06 19:39 ` Lenny Bruzenak
2020-02-07 19:17 ` Steve Grubb
2020-02-07 21:56 ` Paul Moore
2020-02-07 23:17 ` Orion Poplawski
2020-02-10 22:54 ` Paul Moore
2020-02-10 23:05 ` Orion Poplawski
2020-02-10 23:29 ` Casey Schaufler
2020-03-06 16:59 ` Steve Grubb [this message]
2020-02-11 12:58 ` Paul Moore
2020-02-12 21:00 ` Orion Poplawski
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=2633528.kLtZZfLx0Y@x2 \
--to=sgrubb@redhat.com \
--cc=casey@schaufler-ca.com \
--cc=linux-audit@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