From: russell@coker.com.au (Russell Coker)
Date: Tue, 14 Feb 2017 15:14:58 +1100
Subject: [refpolicy] [PATCH 2/2] cups: read permission for
	cupsd_var_run_t socket files in cups_read_pid_files()
In-Reply-To: <7343131.vSoRdTGYPz@russell.coker.com.au>
References: <1486657515.28070.9.camel@trentalancia.net>
	<2374176.zg5KFxEMAR@russell.coker.com.au>
	<7343131.vSoRdTGYPz@russell.coker.com.au>
Message-ID: <4058670.rVs64qVtDq@russell.coker.com.au>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

On Tuesday, 14 February 2017 3:08:28 PM AEDT Russell Coker wrote:
> Does it make sense to have a cups_read_sock_files when the cups clients
> need  read/write access?  Why not just have a single interface granting
> read-write?

I just noticed you added read access to cups_stream_connect so 
cups_read_sock_files is redundant.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/