qyliss changed the topic of #spectrum to: A compartmentalized operating system | https://spectrum-os.org/ | Logs: https://logs.spectrum-os.org/spectrum/
<vilhalmer> there's nothing in the spec for access control, but also nothing preventing the compositor from intervening
<vilhalmer> you could write a custom protocol that gives a specially-designated client the ability to decide who gets to see what
<vilhalmer> (or put it directly in the compositor, but it doesn't really belong there)
<vilhalmer> the sway project might be interested in collaborating on that, I know drew has/had plans for security features that haven't arrived yet
<vilhalmer> like authorizing clients to use a given protocol extension
andi- has quit [Ping timeout: 256 seconds]
andi- has joined #spectrum
cole-h has quit [Ping timeout: 256 seconds]
<qyliss> edef: look at this!!!
<qyliss> Firecracker does userspace vsock
<qyliss> No vhost required
<qyliss> The code looks fairly portable to crosvm too
<MichaelRaskin> Oh nice (re: vsock)
<MichaelRaskin> vilhalmer: well, X11 protocol could also be implemented with each client having an illusion of being alone, unless specially authorised… if wl_roots has some plans to implement filtering, that might be interesting of course.
<MichaelRaskin> Then we get Wayland access control done in an incompatible way between wl_roots/KDE/Gnome, right?
<MichaelRaskin> Hm nice, so Firecracker virtio-vsock is even usable for dynamic multiplexing.
<MichaelRaskin> So such code should be usable for a network-front VM accepting connections from dynamically created network-using VMs
ehmry is now known as ehmry_
ehmry_ has left #spectrum ["https://quassel-irc.org - Chat comfortably. Anywhere."]
<Shell> MichaelRaskin: access control is semi-intentionally not part of Wayland, as xdg-desktop-portal is intended to be the way folks access access-controlled desktop things these days. nobody thought anyone would want to access-control the clipboard though, I imagine. putting the access control stuff in the compositor (or a subprocess thereof) for now seems fine I guess?
<qyliss> I'd surprised nobody thought of access controlling the clipboard, since Qubes does it...
<qyliss> And I'd have assumed Qubes would have come up as an example of access controls in desktop environments
<Shell> qyliss: it could also have been a case of "we need a clipboard to be usable and cba doing access control yet, ship it".
<MichaelRaskin> If anything needs access control, clipboard is in top 3
<edef> qyliss: right, but i wanted vhost-net
<edef> qyliss: like, purposefully
mearon has quit [Quit: WeeChat 1.7.1]
mearon has joined #spectrum
<qyliss> edef: I don't
<qyliss> But yes, I do understand that.
<qyliss> crosvm's implementation is vhost-net
<qyliss> So you get best of both worlds :)
<qyliss> I've been finding it difficult to concentrate for the past couple of days so I think I'm going to take a few days off. Probably won't be on IRC much until then. :)
<qyliss> (that's addressed to the channel, not a response to anybody in particular)
Shell is now known as VShell
VShell is now known as Shell
cole-h has joined #spectrum
<edef> qyliss: :3
erictapen has joined #spectrum
erictapen has quit [Client Quit]
erictapen has joined #spectrum
aranea has quit [Quit: aranea]
erictapen has quit [Ping timeout: 260 seconds]
erictapen has joined #spectrum