** Changed in: chrony (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744662
Title:
finalize a chrony apparmor profile and enable it by default
** Changed in: chrony (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744662
Title:
finalize a chrony apparmor profile and enable it by default
** Changed in: chrony (Debian)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744662
Title:
finalize a chrony apparmor profile and enable it by default
To manage
I like the solution for ipc_owner with a comment and the reference.
That is the best safe&working tradeoff for this case I can think of.
Thanks Jamie!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744
** Changed in: chrony (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744662
Title:
finalize a chrony apparmor profile and enable it by default
To manage notif
This is now done in
https://launchpad.net/ubuntu/+source/chrony/3.2-1ubuntu1 (sorry, I
didn't realize this bug existed).
Here is the upstream submission: https://gitlab.com/apparmor/apparmor-
profiles/merge_requests/10
Here is the Debian bug: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=888
