[apparmor] logs with name="not an absolute path" or name=HEXSTRING
John Johansen
john.johansen at canonical.com
Wed Dec 20 10:00:34 UTC 2017
On 12/20/2017 01:19 AM, Christian Boltz wrote:
> Hello,
>
> Am Mittwoch, 20. Dezember 2017, 06:11:26 CET schrieb John Johansen:
>> On 12/19/2017 06:56 PM, apparmor at raf.org wrote:
>
>>> It means I need to decode paths in log messages before
>>> I can add new rules to make the log messages go away.
>>
>> unfortunately yes. I need to finish a patch to the log parsing lib
>> that will do this transparently, so logprof with just work with
>> this.
>
> Huh? aa-logprof (actually libapparmor) already does the decoding [1], so
> unless I'm overlooking something (not yet handled log fields?), there's
> probably nothing you need to patch ;-)
>
iirc there are a couple of cases that need to be fixed.
More information about the AppArmor
mailing list