Thanks nd, I think your idea for giving access to "others" is best, then individual access can be controlled with SELinux policy, or at least that's the idea, haven't tried it yet in practice.
Re: give unprivileged nspawn container write access to host wayland socket
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: give unprivileged nspawn container write access to host wayland socket
- From: Nozz <nozz@xxxxxxxxxxxxxx>
- Date: Tue, 23 Nov 2021 08:38:53 +0000
- Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
- In-reply-to: <1710ce27-9790-371a-146a-2093d35c78a7@notandy.de>
- References: <Esb4dv4pttIqmYKMftSOhWKp0vBHqDi1NXrmPB52iXNyTx6fXXC80KsLckHm1CdGOiGcAQdxQHm075DVJFQd28ebm6CNOQmc5oZnYoH_b3A=@protonmail.com> <1710ce27-9790-371a-146a-2093d35c78a7@notandy.de>
- Reply-to: Nozz <nozz@xxxxxxxxxxxxxx>
- References:
- Prev by Date: Re: give unprivileged nspawn container write access to host wayland socket
- Next by Date: Re: give unprivileged nspawn container write access to host wayland socket
- Previous by thread: Re: give unprivileged nspawn container write access to host wayland socket
- Next by thread: Re: give unprivileged nspawn container write access to host wayland socket
- Index(es):
 |