[GH-ISSUE #2074] Variables like ${DOWNLOADS} don't seem to work with blacklist #1402

New issue

Closed

opened 2026-05-05 08:04:01 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 08:04:01 -06:00

Owner

Originally created by @chiraag-nataraj on GitHub (Jul 30, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2074

The only variable that seems to work with --blacklist is ${HOME}. I'm going to look into bringing support for the other variables into --blacklist.

Originally created by @chiraag-nataraj on GitHub (Jul 30, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/2074 The only variable that seems to work with `--blacklist` is `${HOME}`. I'm going to look into bringing support for the other variables into `--blacklist`.

gitea-mirror

2026-05-05 08:04:01 -06:00

closed this issue
added the
enhancement
label

gitea-mirror commented

2026-05-05 08:04:04 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Jul 30, 2018):

Hmm, this seems to be a mess because currently, the resolve_xdg and resolve_hardcoded functions in fs_whitelist.c (which would be useful to put in util.c so that it's usable in multiple places) are heavily integrated with the whitelist-specific portions. I will need to refactor a bit so that the parts that are whitelist-specific can be kept in fs_whitelist.c, while the more generic resolver parts can be put in util.c.

@chiraag-nataraj commented on GitHub (Jul 30, 2018): Hmm, this seems to be a mess because currently, the `resolve_xdg` and `resolve_hardcoded` functions in `fs_whitelist.c` (which would be useful to put in `util.c` so that it's usable in multiple places) are heavily integrated with the whitelist-specific portions. I will need to refactor a bit so that the parts that are whitelist-specific can be kept in `fs_whitelist.c`, while the more generic resolver parts can be put in `util.c`.

gitea-mirror commented

2026-05-05 08:04:05 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Jul 31, 2018):

Fixed by 123b2b1e25

@chiraag-nataraj commented on GitHub (Jul 31, 2018): Fixed by 123b2b1e256a17425afa32b238a9c448184f065b

gitea-mirror referenced this issue

2026-05-05 10:10:50 -06:00

[PR #1402] [MERGED] /proc/sys can be nosuid,noexec,nodev #3942