From: guido@trentalancia.com (Guido Trentalancia)
Date: Fri, 14 Jan 2011 00:15:35 +0100
Subject: [refpolicy] refpolicy-2.20101213 (mcs) and dbus messages
In-Reply-To: <4D2F71E7.7030901@gmail.com>
References: <1294867930.1731.34.camel@tesla.lan>
	<4D2EC398.7060304@gmail.com> <1294921531.3112.18.camel@tesla.lan>
	<4D2EF14E.8020903@gmail.com> <1294931759.3153.25.camel@tesla.lan>
	<4D2F1C7B.5040206@gmail.com> <1294946652.2985.19.camel@tesla.lan>
	<4D2F590C.8000005@gmail.com> <1294954622.3100.11.camel@tesla.lan>
	<4D2F71E7.7030901@gmail.com>
Message-ID: <1294960535.3100.14.camel@tesla.lan>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

Hi Dominick !

On Thu, 13/01/2011 at 22.43 +0100, Dominick Grift wrote:
> > But in general for USER_AVCs there is nothing like audit2allow that can
> > be used to ease the job ?
> 
> audit2allow can also be used for these dbus AVC' s sure. But if you want
> this stuff upstreamed then you will have to play by upstreams rules
> (style rules)

No, apparently audit2allow doesn't do the job for USER_AVCs.

Regards,

Guido