pcp
[Top] [All Lists]

Re: [pcp] PCP Updates: pmlogger AF_UNIX socket for normal users; qa vers

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] PCP Updates: pmlogger AF_UNIX socket for normal users; qa version check bump
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Tue, 11 Mar 2014 21:18:23 -0400
Cc: Dave Brolley <brolley@xxxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <98587086.25660473.1394586491367.JavaMail.zimbra@xxxxxxxxxx>
References: <53075D46.6090807@xxxxxxxxxx> <1734063835.17483667.1393481715436.JavaMail.zimbra@xxxxxxxxxx> <53175AAC.5050706@xxxxxxxxxx> <y0ma9d4e93m.fsf@xxxxxxxx> <5318966A.2080600@xxxxxxxxxx> <y0mha7bfg4l.fsf@xxxxxxxx> <98587086.25660473.1394586491367.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mutt/1.4.2.2i
Hi -


> [...]  Checking for just the same uid should suffice for
> full-access.  I think we'll also need to allow uid==zero, else we'll
> need to not risk breaking init scripts.

Yes, except that not all pmloggers will run from init scripts.  Maybe
just leave such policies to the config files instead of hard-coding.


> If/when the full-blown authentication exchange is done (like pmcd),
> we should add the user/group ACLs in here too [...]

(I guess, if someday someone can show a need.  I wouldn't rush.)


> > The same-UID one is arguable.  A person may want to prevent accidental
> > runtime modification of his logger, even by his own future processes.
> 
> That doesn't make sense to me.  Said person cannot prevent himself (?!)
> from sending signals to his own pmlogger, which can already cause change
> (e.g. start new volume via sighup, termination via sigkill, etc).

Yeah, I know it's a stretch.  But if we'll make it configurable, this
would fit in fine.  (Plus sighup/sigkill are more noticeable/traced
than pmlc-driven changes.)


- FChE

<Prev in Thread] Current Thread [Next in Thread>