apparmor profile prevents syslog-ng startup (fix included)

Bug #1739909 reported by nyronium
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AppArmor Profiles
Fix Released
Undecided
Unassigned

Bug Description

Tested on gentoo, syslog-ng-3.13.2, apparmor-profiles-2.11.1-r2;

The apparmor-profile for syslog-ng prevents syslog-ng from accessing /dev/kmsg, which in turn leads to a failure when starting the daemon. This occurs when using a source similar to this one:

    source kernsrc {
        file("/proc/kmsg");
    };

Even though the file should be accessed through /proc/kmsg, syslog-ng checks some conditions on /dev/kmsg before proceeding (checked with strace). As this file is not allowed to be read by the apparmor profile, syslog-ng fails to start.

To fix this issue, simply add this permissions line to the apparmor profile:

    /dev/kmsg r,

Revision history for this message
John Johansen (jjohansen) wrote :

Thanks, I'll get this checked into apparmor for 2.11.2

Revision history for this message
Tyler Hicks (tyhicks) wrote :

A fix for this bug was released in AppArmor 2.12. The upstream commit is e55583ff27308e3338b5c046de42536bbdd48120

Changed in apparmor-profiles:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.