[GH-ISSUE #276] Unexpected behaviour of --whiltelist option when no whitelisted files exist #190

New issue

Closed

opened 2026-05-05 05:17:06 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 05:17:06 -06:00

Owner

Originally created by @manevich on GitHub (Feb 3, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/276

How to reproduce:
firejail --whitelist=/home/user/no-such-file-1 --whitelist=/home/user/no-such-file-2

Result: intact /home/user/ directory.
Expected result: same almost-empty /home/user/ directory as with firejail --private.

If at least one of whitelisted files exist, everything works as excepted.

Originally created by @manevich on GitHub (Feb 3, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/276 How to reproduce: `firejail --whitelist=/home/user/no-such-file-1 --whitelist=/home/user/no-such-file-2` Result: intact `/home/user/` directory. Expected result: same almost-empty `/home/user/` directory as with `firejail --private`. If at least one of whitelisted files exist, everything works as excepted.

gitea-mirror

2026-05-05 05:17:06 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:17:11 -06:00

Author

Owner

@netblue30 commented on GitHub (Feb 9, 2016):

Fixed!

@netblue30 commented on GitHub (Feb 9, 2016): Fixed!

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#190

No description provided.

Rows
Columns