-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--netlock does not work (Error: no valid sandbox) #5312
Labels
bug
Something isn't working
Comments
Thanks for the bug, something went wrong in the last release. Fixed on mainline! |
In that case, can this be closed? I cannot reproduce the error with the following command: firejail --net=eth0 --netlock --noprofile /bin/sh -c 'sleep 70' |
closing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Attempting to pass --netlock doesn't seem to be recognized by firejail - there is no terminal indication of it being present (as was demonstrated in the demo video for netlock's release), and I am able to access other networks that have not been connected to well after the default 1 minute timeout.
I also seem to get the following output in any command that I run which contains --netlock:
Error: no valid sandbox
It seemingly makes no difference as to which command is run, or if I include the --net option as specified as required for --netlock
It should also be noted that the error appears with a delay. For example, running
nano
will cause the error to appear inside of the text editor. Runninghtop
will cause the error to appear as new lines as the bottom of the screen. Running a command/program which has a longer startup will show up as a normal line of logs in a terminal.Steps to Reproduce
firejail --net=eth0 --netlock --noprofile *any command*
firejail --netlock --noprofile *any command*
firejail --netlock *any command*
All of the above will still output the same error, and netlock's specific logs are not present anywhere
Expected behavior
I expected netlock to function
Actual behavior
Netlock did not function
Behavior without a profile
Profile has no bearing
Additional context
I'm just trying to limit a program to local network traffic only. This seemed like the easiest way that I could find, since I can control what this device tries to connect to within the first minute or so.
Environment
Checklist
/usr/bin/vlc
) "fixes" it).https://github.com/netblue30/firejail/issues/1139
)browser-allow-drm yes
/browser-disable-u2f no
infirejail.config
to allow DRM/U2F in browsers.--profile=PROFILENAME
to set the right profile. (Only relevant for AppImages)Log
Output of
LC_ALL=C firejail /path/to/program
Nothing from firejail, unless I pass the --netlock option with or without --net=eth0 (then I get:
Error: no valid sandbox
)Output of
LC_ALL=C firejail --debug /path/to/program
No errors other than the previously mentioned
Error: no valid sandbox
when passing --netlock.I ran both firejail with no options, as well as with the options which cause the problem. Note that since
echo
is a short command, the relevant error shows up after the command has finished:Edit: Attempting to use any netfilter options also results in an error:
Error: invalid network filter file *filename*
I've tried the default template configs as well as one that I made myself, none seem to work. Debug doesn't add any additional information or context.
The text was updated successfully, but these errors were encountered: