mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #7046] Hide/Mask firejail process (pid 1) inside sandbox #3464
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#3464
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @liloman on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/netblue30/firejail/issues/7046
Is your feature request related to a problem? Please describe.
Inside the sandbox you leak your sandbox technique and even configuration used
Describe the solution you'd like
Or mask the process name:
Describe alternatives you've considered
Proc hidepid doesnt compete here and breaks firemon. Bublewrap works nice using --as-pid-1
Additional context
Environment
firejail --version):@netblue30 commented on GitHub (Jan 28, 2026):
So basically what you need an equivalent for --as-pid-1 from bwrap:
I'll mark it as an enhancement.
I don't remember why I was rejecting it with an error:
It doesn't make sense not to show the information, I'll look into it, thanks!
@liloman commented on GitHub (Jan 28, 2026):
If if it isn't duabled to hide pid 1 It will fine just mask it inside the sandbox with something like --mask-parent=my-super-process.exe
In the AI era everything counts :)
I think It was grsecurity related :)
PD: I have two more bwrap related proposals but I need first research them
@netblue30 commented on GitHub (Feb 2, 2026):
The error in firemon is real!
It has to do with the way they treat SUID processes in hidepid=2. You will have to run it using sudo.
The fix is in: hide pid 1 by default, although the process is still in the sandbox. I basically blacklist files in /proc directory. And I have a new command option --unhide-pid1 to make it visible.
commit:
d3f182543d@liloman commented on GitHub (Feb 2, 2026):
Niiice 👍
Thanks.
Closing issue so. :)