mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4930] nogroups + wrc prints confusing messages #2826
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#2826
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 (Feb 11, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4930
Description
nogroups+ wrc prints confusing messages.Steps to Reproduce
Expected behavior
Warning: logind not detectedis only shown when there is no logindWarning: nogroups command ignoredis only shown when it is relly ignoredActual behavior
Warning: logind not detectedis shown on logind systemsWarning: nogroups command ignored; cleaning all supplementary groupsmakes no sense and confuses users.Additional context
Environment
Edit by @kmk3: Formatting.
@ghost commented on GitHub (Feb 11, 2022):
Reproduced on Arch Linux. I can definately agree on
Expected behavioras described above. Nice find 👍.@kmk3 commented on GitHub (Feb 11, 2022):
@rusty-snake commented on Feb 11:
Good catch.
I think this probably happens because
check_can_drop_all_groupsis calledmultiple times and at different places (so it probably runs both before and
after the whitelisting).
IIRC I had tried originally to make the checks run only once a startup, which
would be less likely to fail, but it didn't work for some reason.
I think I'll just comment these messages for now until a better solution is
found.