Skip to content
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

feature: build: add --disable-sandbox-check configure flag #6592

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

powerjungle
Copy link
Contributor

@powerjungle powerjungle commented Dec 27, 2024

This flag disables the code which checks whether the current instance of
firejail is running within a sandbox like LXC, chroot or firejail itself.
If we want to develop firejail inside of a sandbox, to keep the "host system"
clean of unnecessary installed dependencies and changes to the system,
we might want to force firejail to run normally, so that we can test different
profiles inside of the sandbox. This is only meant for people who are working
on the firejail code, not someone attempting to run firejail inside of a
sandbox as a user, because it needs to run as root and it can escape the
sandbox easily.

@kmk3 kmk3 changed the title feat: build: new flag --disable-sandbox-check to configure file feature: build: add --disable-sandbox-check configure flag Dec 28, 2024
@kmk3 kmk3 added the enhancement New feature request label Dec 28, 2024
@powerjungle powerjungle force-pushed the feat/run-firejail-in-sandbox-for-testing branch 3 times, most recently from 1f7e9d6 to 422c544 Compare December 28, 2024 16:05
@powerjungle powerjungle force-pushed the feat/run-firejail-in-sandbox-for-testing branch from 422c544 to 5f36f03 Compare December 29, 2024 22:51
This flag disables the code which checks whether the current instance of
firejail is running within a sandbox like LXC, chroot or firejail itself.
If we want to develop firejail inside of a sandbox, to keep the "host system"
clean of unnecessary installed dependencies and changes to the system,
we might want to force firejail to run normally, so that we can test different
profiles inside of the sandbox. This is only meant for people who are working
on the firejail code, not someone attempting to run firejail inside of a
sandbox as a user, because it needs to run as root and it can escape the
sandbox easily.
@powerjungle powerjungle force-pushed the feat/run-firejail-in-sandbox-for-testing branch from 5f36f03 to 108327c Compare December 30, 2024 00:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature request
Projects
Status: In progress
Development

Successfully merging this pull request may close these issues.

2 participants