From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: [PATCH] Reporting file descriptors created by pipe and socketpair Date: Tue, 12 Sep 2006 13:41:55 -0400 Message-ID: <200609121341.55412.sgrubb@redhat.com> References: <20060912162104.GK4144@devserv.devel.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20060912162104.GK4144@devserv.devel.redhat.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Tuesday 12 September 2006 12:21, Alexander Viro wrote: > c) just how do you propose to do "tracking file descriptors"? =A0It's > so trivial to confuse that it's not even funny; pass an SCM_RIGHTS > datagram to yourself and watch that code blow chunks. So, what would be a good way to let them see the file descriptors created= by=20 these two syscalls? The can get the info for socket, open, accept, ... b= ut=20 these two are difficult to get at the information. This might be better as an aux record instead of part of the syscall reco= rd=20 where the field is meaningless for 99.99% of the syscalls. -Steve