Bug#973356: [pkg-apparmor] Bug#973356: apparmor-profiles: complain on syslog-ng opening system.journal until re-enabling profile

Control: severity -1 minor Hi, I'm lowering severity, in line with the description of the package: apparmor-profiles provides various experimental AppArmor profiles. Do not expect these profiles to work out-of-the-box. . These profiles are not mature enough to be shipped in enforce mode by

Bug#973356: [pkg-apparmor] Bug#973356: apparmor-profiles: complain on syslog-ng opening system.journal until re-enabling profile

It is exactly as you said: I didn't remember that following sshguard guide I customized syslog-ng config and this caused that chain of calls. So I need to customize syslog-ng profile too, if I want to enable it. Thanks Il giorno gio 29 ott 2020 alle ore 22:25 Christian Boltz <

Bug#973356: [pkg-apparmor] Bug#973356: apparmor-profiles: complain on syslog-ng opening system.journal until re-enabling profile

Hello, Am Donnerstag, 29. Oktober 2020, 12:43:08 CET schrieb Lorenzo Iannuzzi: > apparmor="ALLOWED" operation="open" profile="syslog- > ng//null-/bin/dash//null-/usr/sbin/sshguard//null-/bin/journalctl" This is interesting[tm] - syslog-ng executed dash, which then executed sshguard, which