From: guido@trentalancia.net (Guido Trentalancia) Date: Thu, 20 Apr 2017 19:46:02 +0200 (CEST) Subject: [refpolicy] [PATCH 1/2] xserver: console device is chr_file and not fifo_file In-Reply-To: <201704210320.10003.russell@coker.com.au> References: <744918107.204924.1492702640247@pim.register.it> <201704210300.13119.russell@coker.com.au> <120408980.202074.1492707796406@pim.register.it> <201704210320.10003.russell@coker.com.au> Message-ID: <1219174358.207758.1492710362372@pim.register.it> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com Hello. The point is that as it is, this patch is still broken. The new xserver interface is not needed and it should be replaced by three new devices interfaces to be called from the udev module (one for creating a generic "fifo_file" device and two for relabeling from/to). I have already submitted several patches and they are still pending, also I am not sure if these two patches are really needed for wider, general use. If Christopher says that they might turn useful for wider, general use, then I can fix them. Otherwise we just drop the two patches. The idea was that the pipe could be created independently of the specific syslog daemon, so that you do not need to patch every syslog daemon you install (in the sense of patching each syslog daemon init script or whatever). Regards, Guido > On the 20th of April 2017 at 19.20 Russell Coker wrote: > > > On Fri, 21 Apr 2017 03:03:16 AM Guido Trentalancia via refpolicy wrote: > > I thought it can be useful. For example, I am creating it through a udev > > rule, because generally files under /dev are created that way. > > > > I have noticed other people are creating it from rsyslog, but I decided to > > avoid doing that, because I think it is not a very general solution. > > The syslogd (whether rsyslog or another) is going to be the only program > writing to it, so it doesn't make much sense to have anything else create it. > > -- > My Main Blog http://etbe.coker.com.au/ > My Documents Blog http://doc.coker.com.au/