[GH-ISSUE #171] blacklist glob doesn't affect dotfiles #119

New issue

Closed

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

gitea-mirror commented

2026-05-05 05:05:33 -06:00

Owner

Originally created by @ghost on GitHub (Nov 29, 2015).
Original GitHub issue: https://github.com/netblue30/firejail/issues/171

Behaviour is shell specific, I guess, but just wanted to note that it is not obvious that when you intend to blacklist all files in a directory by using a glob, then in fact not all files are blacklisted.

Perhaps you can either put this info in the manpage, or add dotfiles whenever * is seen in the path. The first is probably better. Or maybe both are simply unrelated and it's not firejail's problem.

Originally created by @ghost on GitHub (Nov 29, 2015). Original GitHub issue: https://github.com/netblue30/firejail/issues/171 Behaviour is shell specific, I guess, but just wanted to note that it is not obvious that when you intend to blacklist all files in a directory by using a glob, then in fact not all files are blacklisted. Perhaps you can either put this info in the manpage, or add dotfiles whenever \* is seen in the path. The first is probably better. Or maybe both are simply unrelated and it's not firejail's problem.

gitea-mirror

2026-05-05 05:05:33 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:05:40 -06:00

Author

Owner

@netblue30 commented on GitHub (Jun 1, 2016):

Fixed, thanks for the bug!

@netblue30 commented on GitHub (Jun 1, 2016): Fixed, thanks for the bug!

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

No description provided.

Rows
Columns