AppArmor: Explicitly allow netlink raw socket for Supervisor #370
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Supervisor uses netlink raw sockets to get access to udev events sent through netlink. Technically, the rules so far have denied all raw sockets. However, in practice it seems that netlink raw sockets have still been working.
For unknown reasons, in Debian Bookworm that behavior changed: The rule now also denies netlink raw sockets.
This new ruleset starts off with the default setting (where almost everything seems to be denied), and enables explicitly what is needed in Supervisor. In tests this ruleset worked on Home Assistant OS as well as Debian Bookworm.
Fixes: home-assistant/supervisor#4381