Setting loginuid for a process starting at boot

[Maupertuis Philippe]

The process listens on a network port. It receives custom commands that are executed on the server.
Only one remote host can communicate with the host, the user identifies himself on the remote host only.
The goal is to allow the user to run  the same scripts  on a  lot of server in one command.

Please don't tell me it's silly or insecure or that softwares exist to do that in a secure  way.
I would like to be able to at least monitor what happend throughthis channel.
That means the listening process and all its childs where the valuable changes to the system are made.
It's why I was thinking of setting a dedicated loginuid.

Maybe, eventually it would turn in a PAM-aware application with a proper user authentication and my problems will be solved.

If a simple echo does the trick what is the use of audit_setloginuid or pam_loginuid ?
Any root script can defeat audit with a single command.
I am gobsmacked !
I hope I missed something.

Philippe
________________________________________
De : Steve Grubb [sgrubb at redhat.com]
Date d'envoi : lundi 13 janvier 2014 21:16
À : linux-audit at redhat.com
Cc : Eric Paris; Maupertuis Philippe
Objet : Re: Setting loginuid for a process starting at boot

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


Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.