From: guido@trentalancia.net (Guido Trentalancia) Date: Thu, 20 Apr 2017 18:43:26 +0200 (CEST) Subject: [refpolicy] [PATCH 1/2] xserver: console device is chr_file and not fifo_file In-Reply-To: <201704210240.43722.russell@coker.com.au> References: <744918107.204924.1492702640247@pim.register.it> <201704210240.43722.russell@coker.com.au> Message-ID: <1286385009.201283.1492706606464@pim.register.it> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com Hello Russell. Yes, I think you might be right... I was now double-checking it and I think it is probably right as a named pipe as it was. I think the manage interface can be corrected and kept. Regards, Guido > On the 20th of April 2017 at 18.40 Russell Coker wrote > > > On Fri, 21 Apr 2017 01:37:20 AM Guido Trentalancia via refpolicy wrote: > > The xserver module contains two interfaces to handle the xconsole > > device (usually /dev/xconsole). > > > > Unfortunately, it seems that the above mentioned interfaces use the > > wrong file type: fifo (named pipe) instead of character device. > > Which distribution has it as a character device? I've only ever seen it as a > named pipe. > > Here's a snippet from /etc/init.d/rsyslog on Debian/Unstable: > > create_xconsole() { > XCONSOLE=/dev/xconsole > if [ "$(uname -s)" != "Linux" ]; then > XCONSOLE=/run/xconsole > ln -sf $XCONSOLE /dev/xconsole > fi > if [ ! -e $XCONSOLE ]; then > mknod -m 640 $XCONSOLE p > chown root:adm $XCONSOLE > [ -x /sbin/restorecon ] && /sbin/restorecon $XCONSOLE > fi > } > > -- > My Main Blog http://etbe.coker.com.au/ > My Documents Blog http://doc.coker.com.au/