mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6688] Cannot block keyboard/mouse input (multiseat) #3336
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#3336
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 @Sx1Fl0NdqlkM6N4s2pswXKUI0k9FKTaOckLbNXu on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6688
Description
Adding keyboard or mouse to blacklist doesn't work.
Steps to Reproduce
or pointing out devices individually, or using
--noinputflag also shows no results.Additional context
I'd assume it's an intended feature for most users, with no way to turn it off.
My use-case is a multiseat setup where kb&m inputs won't be sent to all selected windows.
Checklist
/usr/bin/vlc) "fixes" it).https://github.com/netblue30/firejail/issues/1139)browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.--profile=PROFILENAMEto set the right profile. (Only relevant for AppImages)@rusty-snake commented on GitHub (Mar 23, 2025):
What did you expected to happen?
Who did you checked? if blacklisting does not work, this would be a security problem. But I don't believe.
Note that neither GUI nor TUI programs read raw kb/m input from device files.
@Sx1Fl0NdqlkM6N4s2pswXKUI0k9FKTaOckLbNXu commented on GitHub (Mar 23, 2025):
Formatting have eaten stars after every directory.
I was simply blacklisting every found device, hoping something would block keyboard and a mouse, because pointing them individually didn't work (i.e. --blacklist=/dev/input/by-id/usb-0000_USB_OPTICAL_MOUSE-event-mouse --blacklist= /dev/input/by-id/usb-0000_USB_OPTICAL_MOUSE-mouse).
I assume it's correct way to blacklist a device, as that's the examples I've seen, and disabling game controllers and similar worked as expected.
I don't know about any of this, I use firejail purely as enable/disable device software.
@kmk3 commented on GitHub (Mar 24, 2025):
As mentioned by @rusty-snake, programs don't simply get raw access to
keyboard/mouse devices (unlike in some cases with gamepads).
Programs usually just listen and respond to key presses, which is mainly
mediated by xorg/wayland (or something nearby in the stack).
So you'd probably have to try configuring things at that level.
Maybe you can allocate specific devices to specific users with xorg, but I'm
not familiar with that.
Anyway, I don't think that this can be solved with firejail since these device
paths are usually handled by something else and firejail effectively runs on
top of it.