On Wed, Dec 20, 2017 at 02:00:34AM -0800, John Johansen wrote:
> iirc there are a couple of cases that need to be fixed.
There's a patch for supporting the proctitle lines at
https://bugs.launchpad.net/apparmor/+bug/1736841
Thanks
signature.asc
Description: PGP signature
--
AppArmor mailing li
John Johansen wrote:
> On 12/19/2017 06:56 PM, appar...@raf.org wrote:
> > Hi,
> >
> > debian9 (with auditd)
> > apparmor-2.11.0-3
> > apparmor-profiles-2.11.0-3
> > apparmor-profiles-extra-1.11
> >
> > I'm seeing odd apparmor log messages where the name parameter
> > is not an absolute file sys
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, appar...@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.
Hello,
Am Mittwoch, 20. Dezember 2017, 06:11:26 CET schrieb John Johansen:
> On 12/19/2017 06:56 PM, appar...@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
On 12/19/2017 06:56 PM, appar...@raf.org wrote:
> Hi,
>
> debian9 (with auditd)
> apparmor-2.11.0-3
> apparmor-profiles-2.11.0-3
> apparmor-profiles-extra-1.11
>
> I'm seeing odd apparmor log messages where the name parameter
> is not an absolute file system path.
The file is disconnected from t
Hi,
debian9 (with auditd)
apparmor-2.11.0-3
apparmor-profiles-2.11.0-3
apparmor-profiles-extra-1.11
I'm seeing odd apparmor log messages where the name parameter
is not an absolute file system path.
They look like:
type=AVC msg=audit(1513725614.403:1142439): apparmor="ALLOWED"
operation="ge
