Package: pipewire
Version: 0.3.15-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I log in with SSH to the root account of a system where pipewire is installed.
* What was the outcome of this action?
A pipewire process is started automatically by systemd:
# systemd-cgls
Control group /:
-.slice
├─user.slice
│ └─user-0.slice
[...]
│ └─user@0.service …
│ ├─app.slice
│ │ ├─pipewire.service
│ │ │ ├─9730 /usr/bin/pipewire
│ │ │ └─9739 /usr/bin/pipewire-media-session
* What outcome did you expect instead?
No pipewire process since it does not seem to be useful for this use case and
it might increase the attack surface of the system.
I do not know if this problem is better fixed in pipewire or systemd...
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE n>
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pipewire depends on:
ii init-system-helpers 1.60
ii libpipewire-0.3-modules 0.3.15-1
ii pipewire-bin 0.3.15-1
pipewire recommends no packages.
pipewire suggests no packages.
-- no debconf information
--
Laurent.
