From: Jan Beulich <jbeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Daniel Smith <dpsmith@apertussolutions.com>
Subject: Re: [PATCH v3] SUPPORT.md: split XSM from Flask
Date: Wed, 4 Sep 2024 11:38:14 +0200 [thread overview]
Message-ID: <1e3ee882-eb60-4828-9766-69b289740950@suse.com> (raw)
In-Reply-To: <ZtgmgL1g_IW2JWUv@macbook.local>
On 04.09.2024 11:21, Roger Pau Monné wrote:
> On Wed, Aug 14, 2024 at 09:44:11AM +0200, Jan Beulich wrote:
>> XSM is a generic framework, which in particular is also used by SILO.
>> With this it can't really be experimental: Arm mandates SILO for having
>> a security supported configuration.
>>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
Thanks.
>> @@ -788,6 +796,13 @@ Please see XSA-77 for more details.
>> The default policy includes FLASK labels and roles for a "typical" Xen-based system
>> with dom0, driver domains, stub domains, domUs, and so on.
>>
>> +### SILO XSM Module
>> +
>> +SILO implements a policy whereby DomU-s can only communicate with Dom0, yet not
>> +with each other.
>
> Might be good to clarify SILO is just like the dummy XSM
> implementation without allowing inter-domain communication, ie:
>
> "SILO extends the dummy XSM policy by enforcing that DomU-s can only
> communicate with Dom0, yet not with each other."
>
> Or similar.
Fine with me - adjusted.
Jan
next prev parent reply other threads:[~2024-09-04 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 7:44 [PATCH v3] SUPPORT.md: split XSM from Flask Jan Beulich
2024-09-04 8:03 ` Ping: " Jan Beulich
2024-09-04 9:21 ` Roger Pau Monné
2024-09-04 9:38 ` Jan Beulich [this message]
2024-09-04 9:54 ` Daniel P. Smith
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=1e3ee882-eb60-4828-9766-69b289740950@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dpsmith@apertussolutions.com \
--cc=julien@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.