[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2018-05-23 Thread Bug Watch Updater 
** Changed in: unbound (Debian)
   Status: New => 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/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package unbound - 1.6.7-1ubuntu1

---
unbound (1.6.7-1ubuntu1) bionic; urgency=medium

  * debian/apparmor: update to allow writing to /run/systemd/notify
(Closes: #867186, LP: #1723900)

 -- Jamie Strandboge   Thu, 22 Feb 2018 19:35:23 +

** Changed in: unbound (Ubuntu)
   Status: Confirmed => 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/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2018-02-22 Thread Simon Déziel 
Thanks Emily!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2018-02-22 Thread Launchpad Bug Tracker 
This bug was fixed in the package unbound - 1.6.5-1ubuntu0.1

---
unbound (1.6.5-1ubuntu0.1) artful-security; urgency=medium

  * apparmor: permit unbound to notify readiness to systemd
   (Closes: #867186, LP: #1723900)

 -- Simon Deziel   Mon, 16 Oct 2017 13:11:12 +

** Changed in: unbound (Ubuntu Artful)
   Status: Confirmed => 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/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2018-02-20 Thread Emily Ratliff 
The updated package for 17.10/Artful has been uploaded to the security-proposed 
ppa.
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
My testing shows that the bug is resolved. Please try it out.
Thanks for providing the debdiff, Simon!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2018-02-19 Thread Thomas Duboucher 
I checked again, to confirm the behavior. After reverting the changes in
/etc/apparmor.d/usr.sbin.unbound:


sudo service apparmor reload

sudo service unbound restart
Job for unbound.service failed because a timeout was exceeded.
See "systemctl  status unbound.service" and "journalctl  -xe" for details.

dig +dnssec SOA iis.se

; <<>> DiG 9.10.3-P4-Ubuntu <<>> +dnssec SOA iis.se
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61659
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 65494
;; QUESTION SECTION:
;iis.se.IN  SOA

;; ANSWER SECTION:
iis.se. 3600IN  SOA ns.nic.se. hostmaster.iis.se. 
1519057201 14400 3600 1814400 14400

;; Query time: 79 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 19 18:52:44 CET 2018
;; MSG SIZE  rcvd: 89


Versus applying the patch again.

sudo service apparmor reload

sudo service unbound restart

dig +dnssec SOA iis.se

; <<>> DiG 9.10.3-P4-Ubuntu <<>> +dnssec SOA iis.se
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3817
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
;; QUESTION SECTION:
;iis.se.IN  SOA

;; ANSWER SECTION:
iis.se. 3600IN  SOA ns.nic.se. hostmaster.iis.se. 
1519057201 14400 3600 1814400 14400
iis.se. 3600IN  RRSIG   SOA 5 2 3600 20180301152001 
20180219152001 65490 iis.se. 
jRZmwmeu1HeAhITwVf27l+3tWG+MenaxsfMDAngDWKQL7XX8ZzS4D2b8 
KfntCeXSY0CLWJIo+jO3FKVOD/zydxyyhFlkovvT9f0QFgR+SMd7O7An 
H+P3UC1aTcudXbFmY3v5v+9UQOB5MXliZO2L3Ceyn6mV3mAq9zCO4jSO gSk=

;; AUTHORITY SECTION:
iis.se. 3600IN  NS  ns.nic.se.
iis.se. 3600IN  NS  ns3.nic.se.
iis.se. 3600IN  NS  i.ns.se.
iis.se. 3600IN  RRSIG   NS 5 2 3600 20180301152001 
20180219152001 65490 iis.se. 
J5a516jlDZgx1kGeL6lzSfqzjbfiCzMO+Mg8R4lSeznkfNYNA50ord6M 
vYc8QZnHsX8ooUkt5uuZGbNIhp6OM7PCP3U6GT/od5Hul+x1Kucvddi3 
0y0vXzmd0thIdve8iqSbhcaZw6SsSZPKsTb93ssgliK/89M5zr8cjOw6 d+A=

;; Query time: 311 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Feb 19 18:54:17 CET 2018
;; MSG SIZE  rcvd: 472

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2018-02-19 Thread Dimitri John Ledkov 
** Information type changed from Public to Public Security

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2018-02-19 Thread Thomas Duboucher 
This bug silently deactivate DNSSEC on systems where Unbound is
installed. The system will fallback to the default resolver and happily
resolve dns queries with invalid signatures.

This should be marked as a security issue.

Problem resolved (no pun intended) with the provided patch, then reloading the 
apparmor configuration.
systemctl reload apparmor.service 
systemctl restart unbound.service

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2018-01-28 Thread Max 
Same issue in Ubuntu 18.04 alpha
And dmesg is spammed full with messages like:

==
[  458.960479] audit: type=1400 audit(1517146114.040:20): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=594 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  459.261996] audit: type=1400 audit(1517146114.342:21): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=603 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  549.460633] audit: type=1400 audit(1517146204.540:22): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=603 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  549.941806] audit: type=1400 audit(1517146205.021:23): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=611 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  639.960932] audit: type=1400 audit(1517146295.040:24): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=611 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  640.314353] audit: type=1400 audit(1517146295.393:25): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=620 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  730.461420] audit: type=1400 audit(1517146385.540:26): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=620 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  730.787530] audit: type=1400 audit(1517146385.866:27): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=629 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  820.961615] audit: type=1400 audit(1517146476.040:28): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=629 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  821.272747] audit: type=1400 audit(1517146476.351:29): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=640 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  911.463247] audit: type=1400 audit(1517146566.540:30): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=640 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
[  911.790331] audit: type=1400 audit(1517146566.869:31): apparmor="DENIED" 
operation="sendmsg" profile="/usr/sbin/unbound" name="/run/systemd/notify" 
pid=760 comm="unbound" requested_mask="w" denied_mask="w" fsuid=108 ouid=0
==

Goes away after adding the "/{,var/}run/systemd/notify w," line.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2018-01-05 Thread Jeff 
Thanks for tracking this down, same issue on Ubuntu 17.10

Resolved by manually applying the patch above

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2017-10-26 Thread Simon Déziel 
I'll hand around on #ubuntu-devel then, thanks Seth!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2017-10-26 Thread Seth Arnold 
Sorry Simon, I don't have any privileges to do so, hopefully someone
doing Ubuntu patch piloting can pick it up.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2017-10-26 Thread Simon Déziel 
@Seth, any chance to get that debdiff uploaded? Would be much
appreciated.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2017-10-21 Thread Haw Loeung 
** Also affects: unbound (Ubuntu Artful)
   Importance: Undecided
   Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2017-10-16 Thread Seth Arnold 
Looks good to me, thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2017-10-16 Thread Simon Déziel 
** Changed in: unbound (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2017-10-16 Thread Ubuntu Foundations Team Bug Bot 
The attachment "unbound-apparmor-sd_notify.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2017-10-16 Thread Simon Déziel 
Here is a debdiff for Artful with the same patch that I attached to the
Debian bug.

** Patch added: "unbound-apparmor-sd_notify.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+attachment/4972700/+files/unbound-apparmor-sd_notify.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2017-10-16 Thread Bug Watch Updater 
** Changed in: unbound (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/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723900] Re: unbound systemctl (re)start fails due to Apparmor profile issue

2017-10-16 Thread Kai Kasurinen 
** Bug watch added: Debian Bug tracker #867186
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867186

** Also affects: unbound (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867186
   Importance: Unknown
   Status: Unknown

** Tags added: apparmor

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900

Title:
  unbound systemctl (re)start fails due to Apparmor profile issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1723900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs