From: "Renaud Métrich" <rmetrich@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: selinux@lists.fedoraproject.org, QEMU <qemu-devel@nongnu.org>
Subject: Re: qemu-ga guest-exec & SELinux
Date: Tue, 21 Jun 2022 10:42:39 +0200 [thread overview]
Message-ID: <330400e6-5a5f-7f59-b93c-0a3dd5ce47b6@redhat.com> (raw)
In-Reply-To: <YrBGm4Aar1DMmy1H@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 2012 bytes --]
Hi there,
I'm the BZ reporter.
I think the safe solution is to provide something similar to what was
done for vmtools: have a context switching to become sort of
"unconfined" domain.
This context switch has to happen only the executor and we already have
a solution, I documented it in the BZ.
I don't think having an additional boolean is necessary, unless we want
to restrict the commands the guest can execute.
Note that on RHEL the functionality is disabled by default ("guest-exec"
is blacklisted), we may add a note in the /etc/sysconfig/qemu-ga file
stating that allowing such command is risky.
Renaud.
Le 6/20/22 à 12:06, Daniel P. Berrangé a écrit :
> On Mon, Jun 20, 2022 at 01:44:05PM +0400, Marc-André Lureau wrote:
>> Hi!
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=2093355 ("AVCs when trying to
>> execute a command through qemu-ga ("guest-exec" command)") describes an
>> issue with fedora/rhel SELinux rules, where some program executions are
>> denied.
>>
>> qemu-ga has "virt_qemu_ga_t" context, and is not allowed to execute
>> binaries that are not "bin_t", iiuc. The suggestion from Renaud Métrich is
>> for qemu-ga exec command to launch the user program through an helper
>> program that would have the virt_qemu_ga_unconfined_exec_t context, and
>> appropriate rules in selinux (similar to fsfreeze-hook rules), so any
>> program can be executed. qemu-ga would thus ship and use that helper, in
>> all OS, to avoid varying code paths.
>>
>> Does that sound reasonable or should we try to find a solution with SELinux
>> rules instead?
> I thought was did not allow qemu-ga to execute binaries at all, regardless
> of whether they're bin_t or not. The 'guest-exec' command is essentially
> a giant hole that defeats the purpose of confining qemu-ga with SELinux
> at all IMHO.
>
> IMHO execution of external commands should only be allowed after toggling
> a SELinux boolean tunable.
>
>
> With regards,
> Daniel
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-06-21 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 9:44 qemu-ga guest-exec & SELinux Marc-André Lureau
2022-06-20 10:06 ` Daniel P. Berrangé
2022-06-21 8:42 ` Renaud Métrich [this message]
2022-06-21 9:30 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=330400e6-5a5f-7f59-b93c-0a3dd5ce47b6@redhat.com \
--to=rmetrich@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=selinux@lists.fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).