mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1685] firemon and proc hidepid not working for regular user #1140
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#1140
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 @atelszewski on GitHub (Dec 18, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1685
Hi,
I have /proc mounted with hidepid like that:
proc on /proc type proc (rw,hidepid=2,gid=2001)I have my user added to the "showpid" group like that:
Using htop, I'm able to view other users' processes.
But when I try firemon --tree, I get:
Error: /proc is mounted hidepid, you would need to be root to run this commandIs there something wrong on my side or firejail's?
Thanks!
--
Best regards,
Andrzej Telszewski
@netblue30 commented on GitHub (Dec 18, 2017):
hidepid will prevent firemon tool to access pid information for root processes. Grab the latest version from git main, and use "firejail --tree" instead. I put some fixes in to allow firejail to access all pid information. You can also run firemon as root (sudo firemon --tree).
@atelszewski commented on GitHub (Dec 19, 2017):
Hi,
I'm using version 0.9.52.
I tried "firejail --tree" and it works, although it gives some errors at the end and I don't know if they are any relevant:
Anyway, I'm not using this functionality heavily and I'm not going to test the git version.
Mostly, I wanted to signal the possible problem and know what is the solution.
You might close this issue, since I'm satisfied with the reply ;-)
Thanks!
--
Best regards,
Andrzej Telszewski
@netblue30 commented on GitHub (Dec 21, 2017):
I put a fix in git for it, thanks!