[PR #6592] [MERGED] feature: add --disable-sandbox-check configure flag #6084

New issue

Closed

opened 2026-05-05 10:50:26 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 10:50:26 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/6592
Author: @powerjungle
Created: 12/27/2024
Status: ✅ Merged
Merged: 1/12/2025
Merged by: @netblue30

Base: master ← Head: feat/run-firejail-in-sandbox-for-testing

📝 Commits (2)

102d760 chore: build: call autoreconf to match new autoconf version
108327c feature: build: add --disable-sandbox-check configure flag

📊 Changes

5 files changed (+436 additions, -321 deletions)

View changed files

📝 config.mk.in (+2 -0)
📝 configure (+416 -321)
📝 configure.ac (+9 -0)
📝 src/firejail/checkcfg.c (+7 -0)
📝 src/firejail/main.c (+2 -0)

📄 Description

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.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/6592 **Author:** [@powerjungle](https://github.com/powerjungle) **Created:** 12/27/2024 **Status:** ✅ Merged **Merged:** 1/12/2025 **Merged by:** [@netblue30](https://github.com/netblue30) **Base:** `master` ← **Head:** `feat/run-firejail-in-sandbox-for-testing` --- ### 📝 Commits (2) - [`102d760`](https://github.com/netblue30/firejail/commit/102d760fa735c1f36a4c2fdd48ff42702550275c) chore: build: call autoreconf to match new autoconf version - [`108327c`](https://github.com/netblue30/firejail/commit/108327c5a0bfda50efcc0ea7545d1691c7f61743) feature: build: add --disable-sandbox-check configure flag ### 📊 Changes **5 files changed** (+436 additions, -321 deletions) <details> <summary>View changed files</summary> 📝 `config.mk.in` (+2 -0) 📝 `configure` (+416 -321) 📝 `configure.ac` (+9 -0) 📝 `src/firejail/checkcfg.c` (+7 -0) 📝 `src/firejail/main.c` (+2 -0) </details> ### 📄 Description 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

gitea-mirror

2026-05-05 10:50:26 -06:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#6084

No description provided.

Rows
Columns