ntp apparmor profile insufficient ipv6 rights
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ntp (Ubuntu) |
Fix Released
|
Medium
|
Jamie Strandboge | ||
Lucid |
Won't Fix
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Jamie Strandboge |
Bug Description
On one of my 10.04LTS systems, ntpd was failing to start with the following error messages. I modified the apparmor profile(
Nov 18 15:02:26 evans ntpd[15656]: ntpd 4.2.4p8@1.1612-o Tue Apr 19 07:08:18 UTC 2011 (1)
Nov 18 15:02:26 evans ntpd[15656]: set_process_
Nov 18 15:02:26 evans ntpd[15656]: precision = 1.000 usec
Nov 18 15:02:26 evans ntpd[15656]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Nov 18 15:02:26 evans ntpd[15656]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Nov 18 15:02:26 evans ntpd[15656]: socket(AF_INET6, SOCK_DGRAM, 0) failed on address ::: Permission denied
Nov 18 15:02:26 evans ntpd[15656]: unexpected error code 13 (not PROTONOSUPPORT|
Nov 18 15:02:26 evans kernel: [368207.847994] type=1503 audit(132164654
ADDITIONAL INFORMATION:
~$ lsb_release -rd
Description: Ubuntu 10.04.2 LTS
Release: 10.04
~$ apt-cache policy ntp
ntp:
Installed: 1:4.2.4p8+
Candidate: 1:4.2.4p8+
Version table:
*** 1:4.2.4p8+
500 http://
100 /var/lib/
1:
500 http://
Related branches
Changed in ntp (Ubuntu): | |
importance: | Undecided → Medium |
milestone: | none → precise-alpha-1 |
Changed in ntp (Ubuntu Precise): | |
status: | Confirmed → Triaged |
no longer affects: | ntp (Ubuntu Hardy) |
Changed in ntp (Ubuntu Precise): | |
milestone: | precise-alpha-1 → precise-alpha-2 |
Changed in ntp (Ubuntu Precise): | |
status: | Triaged → In Progress |
Changed in ntp (Ubuntu Precise): | |
status: | In Progress → Fix Committed |
Thank you for using Ubuntu and reporting a bug. Does adding the following to /etc/apparmor. d/usr.sbin. ntpd fix the problem for you:
network inet6 dgram,
(you'll need to run 'sudo apparmor_parser -r /etc/apparmor. d/usr.sbin. ntpd' after adjusting the profile)