[GH-ISSUE #1019] private-dev not working? #696

Closed
opened 2026-05-05 06:27:54 -06:00 by gitea-mirror · 5 comments
Owner

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?

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?
gitea-mirror 2026-05-05 06:27:54 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@netblue30 commented on GitHub (Jan 4, 2017):

I'll look into it.

<!-- gh-comment-id:270516694 --> @netblue30 commented on GitHub (Jan 4, 2017): I'll look into it.
Author
Owner

@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 --audit results;
GOOD: Access to /dev directory is restricted.
I also tested with the original profile with the same audit results (re: /dev directory)
Tested on Arch Linux, firejail version 0.9.45

<!-- gh-comment-id:275513627 --> @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](https://github.com/saildata/firejail-jailhouse/blob/master/usr/local/bin/firejail-keepassx2) with `--audit` results; `GOOD: Access to /dev directory is restricted.` I also tested with the original profile with the same audit results (re: `/dev` directory) Tested on Arch Linux, firejail version 0.9.45
Author
Owner

@viking777 commented on GitHub (Jan 27, 2017):

Thanks saildata, works for me also.
That's a hell of a long launcher though!

<!-- gh-comment-id:275635871 --> @viking777 commented on GitHub (Jan 27, 2017): Thanks saildata, works for me also. That's a hell of a long launcher though!
Author
Owner

@saildata commented on GitHub (Jan 27, 2017):

@viking777 glad to hear it resolved the issue! Hopefully it's not a bug, then.

<!-- gh-comment-id:275739382 --> @saildata commented on GitHub (Jan 27, 2017): @viking777 glad to hear it resolved the issue! Hopefully it's not a bug, then.
Author
Owner

@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.

<!-- gh-comment-id:368283346 --> @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.
Sign in to join this conversation.
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#696
No description provided.