mirror of
https://passt.top/passt
synced 2025-03-20 07:58:53 +00:00
f66769c2de
If libvirtd is triggered by an unprivileged user, the virt-aa-helper mechanism doesn't work, because per-VM profiles can't be instantiated, and as a result libvirtd runs unconfined. This means passt can't start, because the passt subprofile from libvirt's profile is not loaded either. Example: $ virsh start alpine error: Failed to start domain 'alpine' error: internal error: Child process (passt --one-off --socket /run/user/1000/libvirt/qemu/run/passt/1-alpine-net0.socket --pid /run/user/1000/libvirt/qemu/run/passt/1-alpine-net0-passt.pid --tcp-ports 40922:2) unexpected fatal signal 11 Add an annoying workaround for the moment being. Much better than encouraging users to start guests as root, or to disable AppArmor altogether. Reported-by: Prafulla Giri <prafulla.giri@protonmail.com> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
52 lines
1.9 KiB
Plaintext
52 lines
1.9 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-or-later
|
|
#
|
|
# PASST - Plug A Simple Socket Transport
|
|
# for qemu/UNIX domain socket mode
|
|
#
|
|
# PASTA - Pack A Subtle Tap Abstraction
|
|
# for network namespace/tap device mode
|
|
#
|
|
# contrib/apparmor/usr.bin.passt - AppArmor profile for passt(1)
|
|
#
|
|
# Copyright (c) 2022 Red Hat GmbH
|
|
# Author: Stefano Brivio <sbrivio@redhat.com>
|
|
|
|
abi <abi/3.0>,
|
|
|
|
include <tunables/global>
|
|
|
|
profile passt /usr/bin/passt{,.avx2} {
|
|
include <abstractions/passt>
|
|
|
|
# Alternatively: include <abstractions/user-tmp>
|
|
owner /tmp/** w, # tap_sock_unix_open(),
|
|
# tap_sock_unix_init(), pcap(),
|
|
# pidfile_open(),
|
|
# pidfile_write(),
|
|
# logfile_init()
|
|
|
|
owner @{HOME}/** w, # pcap(), pidfile_open(),
|
|
# pidfile_write()
|
|
|
|
# Workaround: libvirt's profile comes with a passt subprofile which includes,
|
|
# in turn, <abstractions/passt>, and adds libvirt-specific rules on top, to
|
|
# allow passt (when started by libvirtd) to write socket and PID files in the
|
|
# location requested by libvirtd itself, and to execute passt itself.
|
|
#
|
|
# However, when libvirt runs as unprivileged user, the mechanism based on
|
|
# virt-aa-helper, designed to build per-VM profiles as guests are started,
|
|
# doesn't work. The helper needs to create and load profiles on the fly, which
|
|
# can't be done by unprivileged users, of course.
|
|
#
|
|
# As a result, libvirtd runs unconfined if guests are started by unprivileged
|
|
# users, starting passt unconfined as well, which means that passt runs under
|
|
# its own stand-alone profile (this one), which implies in turn that execve()
|
|
# of /usr/bin/passt is not allowed, and socket and PID files can't be written.
|
|
#
|
|
# Duplicate libvirt-specific rules here as long as this is not solved in
|
|
# libvirt's profile itself.
|
|
/usr/bin/passt r,
|
|
owner @{run}/user/[0-9]*/libvirt/qemu/run/passt/* rw,
|
|
owner @{run}/libvirt/qemu/passt/* rw,
|
|
}
|