http://bugzilla.opensuse.org/show_bug.cgi?id=954104 Per Jessen changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |peter@czanik.hu |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=954104 http://bugzilla.opensuse.org/show_bug.cgi?id=954104#c2 Per Jessen changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|peter@czanik.hu |suse-beta@cboltz.de --- Comment #2 from Per Jessen --- I ran aa-logprof and let it update the profile: # aa-logprof Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. Enforce-mode changes: Profile: syslog-ng Path: /run/log/journal/ Mode: r Severity: unknown [1 - /run/log/journal/] (A)llow / [(D)eny] / (I)gnore / (G)lob / Glob with (E)xtension / (N)ew / Abo(r)t / (F)inish / (M)ore However, apparmor wasn't happy with that (output from systemctl status apparmor): Dec 04 12:57:00 office34 boot.apparmor[8679]: Restarting AppArmor AppArmor parser error for /etc/apparmor.d/sbin.syslog-ng in /etc/apparmor.d/tunables/home at line 16: syntax error, unexpected TOK_SET_VAR, expecting TOK_VALUE Dec 04 12:57:00 office34 boot.apparmor[8679]: /etc/apparmor.d/sbin.syslog-ng failed to load..failed Dec 04 12:57:00 office34 boot.apparmor[8679]: AppArmor parser error for /etc/apparmor.d/sbin.syslog-ng in /etc/apparmor.d/tunables/home at line 16: syntax error, unexpected TOK_SET_VAR, expecting TOK_VALUE Dec 04 12:57:00 office34 boot.apparmor[8679]: ..done -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=954104 http://bugzilla.opensuse.org/show_bug.cgi?id=954104#c4 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |AppArmor --- Comment #4 from Christian Boltz --- The problematic change in the profile is: -@{CHROOT_BASE}="" +@{CHROOT_BASE} = Re-add the empty quotes to make the profile valid again. (This is fixed upstream already and will be included in the next upstream release.) I'm surprised about those removals: - unix (receive) type=dgram, - unix (receive) type=stream, which uncovers a bug in the tools - they store the unix rules when reading the profile, but don't write them back to it. I opened a bug upstream: https://bugs.launchpad.net/apparmor/+bug/1522938 and will create a patch soon. For the journal, I added the following rules upstream about a month ago: /{var,var/run,run}/log/journal/ r, /{var,var/run,run}/log/journal/*/ r, /{var,var/run,run}/log/journal/*/*.journal r, This covers your report and some additional needs. So 2 of 3 things you noticed and accidently ;-) noticed are already fixed upstream. Expect a maintenance update as soon as AppArmor 2.10.1 gets released ;-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=954104 http://bugzilla.opensuse.org/show_bug.cgi?id=954104#c9 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #9 from Christian Boltz --- The fixes for this bug are on their way to Factory and 42.1. -- You are receiving this mail because: You are on the CC list for the bug.