mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #5545] /proc/config.gz blacklisted twice #3029
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#3029
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 @ghost on GitHub (Dec 21, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5545
Minor issue with blacklisting kernel configuration:
6e67801a45/etc/inc/disable-common.inc (L624)6e67801a45/etc/inc/disable-proc.inc (L11)Not sure which of these include files would be the better place for it. I've checked our profiles and there are zero files that include disable-proc.inc without also including disable-common.inc, so it won't be a lot of work to remove it from one or the other. Or am I missing something here and it's supposed to be like this?
@kmk3 commented on GitHub (Dec 21, 2022):
Since disable-common.inc is the more, well, common include I'd leave it only
there.
Alternatively, put something like this in disable-proc.inc:
To make it clear that the duplication is intentional.
@rusty-snake commented on GitHub (Dec 21, 2022):
Correct. But disable-proc should really disable proc and not depend on dc for full functionality.
I'd say dp must have it and we should keep it in dc as legacy blacklist for now.
OT: disable-proc can and should be used in much more profiles.
@ghost commented on GitHub (Dec 21, 2022):
Agreed. Now we just made it a bit more visible via the comment. Might avoid future mishaps if someone tries to remove it from dc.
Indeed. Not sure we can do the work to get it into 0.9.72. The same goes for
noprintersIMO.