TL;DR - not the same bug, please open a new one Hi, well I only explained how to avoid the issue of the self FD access. This is what this bug is about.
And your report doesn't have that anymore. Please open a new bug for your issue. For the things I see in what you posted seems to be about resolve.conf updates driven by/through strongswan. That really is a different issue. The line: #include <abstractions/nameservice> Should cover resolve.conf actions, but we'd have to understand exactly how your strongswan is configured triggering this issue and then consider what/where to add apparmor rules for. Please just use your last post for a new bug and feel free to copy&paste my reply as an answer. >From there add your config details especially related to resolve.conf updating and we can start thinking about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786250 Title: strongswan (charon) is rejected by apparmor to read /proc/<PID>/fd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1786250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
