mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1019] private-dev not working? #696
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#696
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 @viking777 on GitHub (Jan 3, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1019
The following profiles which I use all have 'private-dev' in their profile files:
thunderbird, keepassx, evince, opera, vlc, libreoffice.
However an audit of any of them always gives the warning:
"/dev directory seems to be fully populated. Use --private-dev or --whitelist to restrict the access."
Does this mean that the 'private-dev' option is not working?
@netblue30 commented on GitHub (Jan 4, 2017):
I'll look into it.
@saildata commented on GitHub (Jan 26, 2017):
In case it helps confirm/working as expected for this ticket:
I use a slightly modified launcher for keepassx2 with
--auditresults;GOOD: Access to /dev directory is restricted.I also tested with the original profile with the same audit results (re:
/devdirectory)Tested on Arch Linux, firejail version 0.9.45
@viking777 commented on GitHub (Jan 27, 2017):
Thanks saildata, works for me also.
That's a hell of a long launcher though!
@saildata commented on GitHub (Jan 27, 2017):
@viking777 glad to hear it resolved the issue! Hopefully it's not a bug, then.
@Fred-Barclay commented on GitHub (Feb 25, 2018):
I can't replicate this today (firejail 0.9.52)... let's close for now and reopen if we need to.