This should be fixed in Ubuntu 19.04.
** Changed in: fwknop (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/1598506
Title:
apparmor profile prevents
** Changed in: fwknop (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/1598506
Title:
apparmor profile prevents fwknop-server from starting
To manage
** Changed in: fwknop (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/1598506
Title:
apparmor profile prevents fwknop-server from starting
To manage
These fixes got merged upstream in 2.6.10:
https://github.com/mrash/fwknop/commit/86bd1ea1e6eac04f938d9d13816a6fa0b1e3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598506
Title:
apparmor
** Bug watch added: Debian Bug tracker #911485
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911485
** Also affects: fwknop (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911485
Importance: Unknown
Status: Unknown
--
You received this bug notification because
If you run fwknopd within an LXC container for example, the problem does
NOT occur. Maybe the underlying apparmor rules for the container allow
certain operations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This problem only occurs if the package "fwknop-apparmor-profile" is
installed as well, which is creating the apparmor profile for fwknopd in
/etc/apparmor.d/usr.sbin.fwknopd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problems seems to be apparmor, which is restricting permissions.
Problem can be solved by changing the file
/etc/apparmor.d/usr.sbin.fwknopd and add the following lines:
/run/xtables.lock rwk,
network inet dgram,
network inet6 dgram,
--
You received this bug notification because you
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fwknop (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/1598506
Title:
