Chromium sandbox tracking bug.
- Dominant language
- C++
- Stars
- 8k
- Forks
- 351
- Avg merge
- 12h 31m
- Merged PRs (30d)
- 102
Description
Chromium applications executed under FEX can't correctly use their sandbox in our environment currently.
Usually this can be resolved by passing the application `--no-sandbox` which will disable the sandbox.
Not all applications support this, and some will refuse to run if passed that option.
At some point FEX needs to support running the sandbox environment but this will be a tracking bug when we find applications that hit this issue.
Known applications that use chromium's sandbox
- ~~steamwebhelper~~
- Mathpix snippping tool
- Chrome/Chromium
- anki flashcards
- Some game launchers that I need to find again
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reproducing the sandbox failure with the listed Chromium-based applications in FEX, then identify the affected sandbox path; done means supported applications run without requiring --no-sandbox.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100