mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #335] make whitelist file names a bit more permissive (allowed characters) #236
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#236
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 @vn971 on GitHub (Feb 28, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/335
Currently firejail
whitelistfails with the following letters:[](){}Unfortunately though, these letters are often used by some cultures, like for example torrent video files. It'd be nice if firejail supported those [names].
This is a delicate topic though, suggestions or criticism welcome. For example, I personally would not include
&or$as good file names.@netblue30 commented on GitHub (Mar 6, 2016):
moved to: https://github.com/netblue30/firejail/issues/216
@vn971 commented on GitHub (May 2, 2016):
Any update on this? The #216 ticket does not address special characters
[](){}...@netblue30 commented on GitHub (May 2, 2016):
None so far. I updated #216