apparmor errors with current ntp

Bug #1647586 reported by LaMont Jones
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ntp (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

On ntpd restart, this gets logged. (1:4.2.8p8+dfsg-1ubuntu2)

Dec 6 01:14:05 rover3 kernel: [16526.813113] audit: type=1400 audit(1481012045.534:136): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=29435 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=123 ouid=0

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

This should be fixed by add the rule

   dbus rw peer=(name=/run/dbus/system_bus_socket),

the /usr/sbin/ntpd profile

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi LaMont, I recently looked into ntp apparmor messages, but only found a few non critical ones and a few that only occur in lxd which are fixed already.

On none of these tests I saw this message - is that part of a particular setup/config to trigger this?

Changed in ntp (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ntp (Ubuntu) because there has been no activity for 60 days.]

Changed in ntp (Ubuntu):
status: Incomplete → Expired
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.