mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1148] nogroups option and man page #794
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#794
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 @SYN-cook on GitHub (Mar 19, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1148
I have found a deviation between man page and actual firejail behavior. When I run first
firejail --nogroupsand then theidcommand, the output still shows few supplementary groups:uid=1000(user) gid=1000(user) Gruppen=1000(user),65534,29(audio),65534,44(video),65534Also I have no idea what's behind gid 65534(that was an easy one - it's group nogroup).According to the man page I would expect something more restrictive like:
uid=1000(user) gid=1000(user) Gruppen=1000(user)This is on Debian (Jessie and Stretch) with firejail 0.44.8 and 0.45
@netblue30 commented on GitHub (Mar 20, 2017):
It is a bug! --noroot does something similar with --nogroups, but allows audio, video, games and tty groups. I'll have to clean them up.
65534 is user/group nobody:
I'll try to find out why is added by default. Anyway, the guy has no permissions whatsoever. I see it used mainly by servers.
@netblue30 commented on GitHub (Mar 20, 2017):
Fixed!