From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: auditing file based capabilities
Date: Mon, 13 Oct 2008 07:15:42 -0400
Message-ID: <200810130715.43092.sgrubb@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
Content-Disposition: inline
List-Unsubscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: Linux Audit <linux-audit@redhat.com>
List-Id: linux-audit@redhat.com

Hi,

With file based capabilities in recent kernels, I think we need to add those 
to the path records. An example PATH record:

node=127.0.0.1 type=PATH msg=audit(1223893548.459:459): item=1 
name="/etc/resolv.conf" inode=20774937 dev=08:08 mode=0100644 ouid=0 ogid=0 
rdev=00:00 obj=system_u:object_r:net_conf_t:s0

If executing the file leads to extra capabilities, I think we need to record 
that. If we add it, I'd like to see it recorded like render_cap_t does for 
the proc filesystem. In order to conserve disk space, should we make the 
field optional so that it doesn't appear in the record unless there are file 
based capabilities?

Thanks,
-Steve