From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Setting loginuid for a process starting at boot Date: Mon, 13 Jan 2014 15:16:21 -0500 Message-ID: <1583332.IZPiC8c0Xe@x2> References: <1389643975.15435.16.camel@flatline.rdu.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1389643975.15435.16.camel@flatline.rdu.redhat.com> 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 Cc: Maupertuis Philippe List-Id: linux-audit@redhat.com On Monday, January 13, 2014 03:12:55 PM Eric Paris wrote: > On Sun, 2014-01-12 at 23:00 +0100, Maupertuis Philippe wrote: > > Hi, > > > > I want to monitor a process which starts at boot. > > > > I would like to assign it a specific loginuid for that purpose. > > > > What is the best way to do that ? > > Have the init script echo a value into /proc/self/loginuid ? The loginuid is supposed to be used only for real user sessions. The daemon would not normally qualify as a user session. I suspect that this is needed because we have no way to audit by process name. I suspect that is the real issue that leads to needing to use the loginuid for something it was not intended for. -Steve