Fix bwrap loopback permission error in secure mode#21
Closed
nbeerbower wants to merge 2 commits into
Closed
Conversation
Setting up loopback in a new network namespace requires CAP_NET_ADMIN, which unprivileged users don't have. This caused the error: "bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted" Network restrictions are still enforced by hemlock's --sandbox flag. All other isolation (user, PID, filesystem, IPC) remains intact.
When user namespaces aren't available (common on Ubuntu 24.04+ due to AppArmor restrictions), Grove now falls back to basic sandbox mode with a helpful message showing how to enable them, instead of failing with "bwrap: setting up uid map: Permission denied".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Setting up loopback in a new network namespace requires CAP_NET_ADMIN, which unprivileged users don't have. This caused the error: "bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted"
Network restrictions are still enforced by hemlock's --sandbox flag. All other isolation (user, PID, filesystem, IPC) remains intact.