mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2695] reboot works with --seccomp #1696
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#1696
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 @berezhinskiy on GitHub (May 14, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2695
Firejail version 0.9.52
I expect that reboot will be denied due to --seccomp option.
Nevertheless, reboot works. Here is output:
@SkewedZeppelin commented on GitHub (May 14, 2019):
Are you running systemd? those are probably invoked through dbus or the like.
Try with
--nodbus --net=none@berezhinskiy commented on GitHub (May 14, 2019):
9.52 has no --nodbus option. I compile latest (0.9.60~rc1), result is the same:
I'm using clean Ubuntu 18.04.2
Thank you.
@topimiettinen commented on GitHub (May 15, 2019):
--nodbusactually blocks access only to user session D-Bus (socket path/run/user/UID/dbus).rebootcommand under systemd connects to system D-Bus with different path (/run/dbus/system_bus_socket), so it is not blocked. Seccomp filters would block ifrebootcommand attempted to use system callreboot(2)directly, which would happen withreboot -f -fbut not in your case.We could add a new option to block system d-bus, or make
--nodbusblock that also.SysV
rebootcommand talked to PID 1 via/dev/initctlpipe and also systemd has compatibility for that. Perhaps that path (and/run/initctl) should be blocked too in your case, but it's not related to d-bus anymore. IIRC rebooting was not possible for unprivileged users under SysV, so it may not be necessary.@rusty-snake commented on GitHub (May 15, 2019):
@topimiettinen you reminded me that if you use systemd, you can use polkit to define permissions for unpreveiled users to use reboot (halt, suspend, ...).
@topimiettinen commented on GitHub (May 15, 2019):
I made PR #2697, which makes
--nodbusblock also system bus.@rusty-snake commented on GitHub (May 15, 2019):
Just as an basic idea:
/etc/polkit-1/rules.d/50-deny-firejailed-reboots.rules
@Vincent43 commented on GitHub (May 15, 2019):
I think
--nodbusshould block all dbus without additional polkit hacks.@Vincent43 commented on GitHub (May 17, 2019):
I think we can count this as fixed by https://github.com/netblue30/firejail/pull/2697