apparmor profile prevents fwknop-server from starting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fwknop (Debian) |
Fix Released
|
Unknown
|
|||
fwknop (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I had to remove the fwknop-
$ sudo service fwknop-server status
● fwknop-
Loaded: loaded (/etc/init.
Active: active (exited) since ven 2016-07-01 20:17:33 PDT; 56min ago
Docs: man:systemd-
Process: 8468 ExecStart=
jui 01 20:17:33 egilsstadir systemd[1]: Starting LSB: start and stop fwknopd...
jui 01 20:17:33 egilsstadir fwknop-
jui 01 20:17:33 egilsstadir fwknop-
jui 01 20:17:33 egilsstadir systemd[1]: Started LSB: start and stop fwknopd.
jui 01 20:17:33 egilsstadir fwknopd[8506]: Starting fwknopd
jui 01 20:17:33 egilsstadir fwknopd[8506]: Added jump rule from chain: INPUT to chain: FWKNOP_INPUT
jui 01 20:17:33 egilsstadir fwknopd[8506]: iptables 'comment' match is available
jui 01 20:17:33 egilsstadir fwknopd[8506]: Sniffing interface: eth0
jui 01 20:17:33 egilsstadir fwknopd[8506]: [*] pcap_open_live() error: socket for SIOCETHTOOL(
Changed in fwknop (Debian): | |
status: | Unknown → New |
Changed in fwknop (Debian): | |
status: | New → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.