From: guido@trentalancia.com (Guido Trentalancia)
Date: Sat, 15 Jan 2011 16:06:01 +0100
Subject: [refpolicy] refpolicy-2.20101213 (mcs) and dbus messages
In-Reply-To: <4D301895.3050409@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> <1294960535.3100.14.camel@tesla.lan>
	<4D301895.3050409@gmail.com>
Message-ID: <1295103962.3458.8.camel@tesla.lan>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

Hello Dominick,

just a quick note, to correct myself.

On Fri, 14/01/2011 at 10.34 +0100, Dominick Grift wrote:
> > 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.
> 
> Strange, in that case i guess you will have to translate it manually.

Of course, audit2allow also works on USER_AVC audit messages !

So the other day, either the formatting went lost, because I was doing
copy&paste from the full audit logs to newly created partial logs, or
otherwise I had used illegal characters such as underscore in partial
log file names thus breaking up the script that I am using and which
generates module names from file names...

Sorry about that.

Regards,

Guido