On Thu, 22 May 2025 21:02:48 +
"Sloane, Brandon" wrote:
> > Could you explain more of your actual use cases? Maybe people would
> > have better ideas how to solve them.
>
> We are focused on cross domain and multi-level systems built using
> SELinux as a core part of their security archite
ing is the source wl_data_source; this does require explicit compositor
support to provide. The wl_surface was relevent for screenshots.
-- Brandon
> -Original Message-
> From: Pekka Paalanen
> Sent: Thursday, May 22, 2025 4:58 AM
> To: Sloane, Brandon
> Cc: wayland-devel
On Tue, 20 May 2025 19:11:06 +
"Sloane, Brandon" wrote:
> > -Original Message-
> > From: Pekka Paalanen
> > Sent: Tuesday, May 20, 2025 4:58 AM
> > To: Sloane, Brandon
> > Cc: wayland-devel@lists.freedesktop.org
> > Subject: Re: [RFC
From: Alyssa Ross
Sent: Wednesday, May 21, 2025 1:28 PM
To: Sloane, Brandon
Cc: wayland-devel@lists.freedesktop.org; Pekka Paalanen
Subject: RE: [RFC] Wayland Security Modules
"Sloane, Brandon" writes:
>> -Original Message-
>> From: Pekka Paalanen
>
"Sloane, Brandon" writes:
> I'm not sure how the pop-os/cosmic-comp PR is relevent. It seems to be about
> exposing cosmic-comp as a library in general. While potentially useful,
> several other compositors have been doing that for a while, and it doesn't
> seem inform security decisions.
Yea
"Sloane, Brandon" writes:
>> -Original Message-
>> From: Pekka Paalanen
>> Sent: Tuesday, May 20, 2025 4:58 AM
>> To: Sloane, Brandon
>> Cc: wayland-devel@lists.freedesktop.org
>> Subject: Re: [RFC] Wayland Security Modules
>>
>&
> -Original Message-
> From: Pekka Paalanen
> Sent: Tuesday, May 20, 2025 4:58 AM
> To: Sloane, Brandon
> Cc: wayland-devel@lists.freedesktop.org
> Subject: Re: [RFC] Wayland Security Modules
>
> On Mon, 19 May 2025 15:48:04 +
> "Sloane, Brandon&quo
On Mon, 19 May 2025 15:48:04 +
"Sloane, Brandon" wrote:
> Hello,
>
> I've spent the past few months prototyping a security modules system
> for Wayland. Our specific motivation for this is to support SELinux
> integration to meet some rather unique security requirements.
> However, what we a
