vuinputd/docs/DESIGN.md
2025-10-24 21:46:18 +00:00

2.9 KiB
Raw Blame History

Design Document

1. Introduction

This project provides a safe way to run Sunshine inside systemd-nspawn containers. Sunshine requires creating virtual input devices (/dev/uinput) for keyboards, mice, and controllers.

Naively exposing /dev/uinput from the host into a container breaks isolation: containers could create devices visible to other containers, and the host could even start consuming those devices.


2. Architecture

Usually, uinput apps like sunshine open the /dev/uinput interface of the kernel to create a new artificial event device like /dev/input/event9

sequenceDiagram
uinput apps->>uinput (kernel): open /dev/uinput and setup
create participant eventx
uinput (kernel)->>eventx: create /dev/input/eventx
uinput (kernel)->>libinput/game: announce new device via udev
libinput/game->>eventx: open /dev/input/eventx

vuinputd provides a virtual uinput called /dev/vuinput that can be bind-mounted as /dev/uinput in the container. Thus, uinput devices can also be created inside containers:


sequenceDiagram
box transparent Host
participant uinput (kernel)
participant vuinputd
participant vuinput (host)
end

box transparent Container
participant uinput (container)
participant uinput apps
participant eventx
participant libinput/game
end

vuinputd->>vuinput (host): create /dev/vuinput with cuse
uinput apps->>uinput (container): open /dev/uinput and setup
uinput (container)-->vuinput (host): is equal (bind mount)
vuinput (host)->>vuinputd: forward data
vuinputd->>uinput (kernel): forward data
uinput (kernel)->>eventx: create /dev/input/eventx
uinput (kernel)->>vuinputd: announce new device via udev
vuinputd->>libinput/game: announce new device via udev
libinput/game->>eventx: open /dev/input/eventx

3. Design Decisions

3.1 Where /dev/uinput lives

  • Decision: Provide a fake /dev/vuinput backed by host proxy. This character device can be bind mounted inside containers to /dev/uinput.
  • Why: Prevents containers from creating devices visible system-wide.

3.2 Prevent host from using devices

  • Decision: udev rules strip ID_INPUT_KEYBOARD and ID_INPUT_MOUSE, set ID_SEAT=seat_vuinput.
  • Why: Ensures devices are invisible to host input subsystems while still available in containers.

3.3 udev events in containers

  • Decision: Proxy forwards udev events into the container via netlink.
  • Why: Without this, SDL2 and libinput might not recognize devices correctly; with it, containers behave as if devices were created locally.

3.4 Where to run the proxy

  • Decision: Run proxy on host, one instance per container.
  • Why: Only host can safely access /dev/uinput and enforce mediation.

3.5 Security trade-off

  • Decision: Accept that host always sees devices, but enforce rules to stop it consuming them.
  • Why: Full input namespaces dont exist in Linux today; mediation is the practical compromise.