mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4454] Merge disable-passwordmgr.inc in disable-common.inc or disable-programs.inc #2675
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#2675
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 @rusty-snake on GitHub (Aug 6, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4454
While working on #4157 I was wondering why why treat configurations of password-managers special. (At least of KPXC) there are no secrets in the
blacklisted paths, only config/state files. There are more "problematic" files in disable-programs.inc like~/.mozilla(your firefox profile) or~/.config/mpv(code execution). Should we merge disable-passwordmgr.inc in disable-programs.inc?@reinerh commented on GitHub (Aug 6, 2021):
I think a reason to have it separate could have been that it's "easier" to just include
disable-passwordmgr.inceverywhere without having to fear to break something (as the blacklisted file are very secret, it's good to include it whereever possible). Includingdisable-programs.inccan probably not be done so "blindly".But I'm fine with merging it with one of your suggested files. I even just noticed that the other two files are included about the same time as disable-passwordmgr:
@rusty-snake commented on GitHub (Aug 6, 2021):
That's the point, they aren't secret (at least keepassxc).
There's no reason other programs need to access these file.
~/.config/keepassxc/keepassxc.iniIf bitwarden/lastpass/... users can say something it would be great.
I don't think that these few are worth to have an own disable include.
Maybe a
allow-passwdmgr.incmakes more sense. If there are any programs that would use this.