Design a security interface about wlroots HOT 4 CLOSED

This is... way more than necessary.

All wlroots needs to do for now is make a hook available on the i.e. wlr_screenshooter as bool (*bind)(struct wlr_screenshooter *shooter, struct wl_client *client);. The compositor can return false if they don't want that client to bind to this interface. Simple as that.

from wlroots.

We can use the filtering approach as well, but again that doesn't require any input from our side. The compositor has access to the wl_display and can do whatever they want with it.

from wlroots.

I agree with @SirCmpwn, the current setup is fine. Let the compositors deal with it by exposing the hooks.

from wlroots.

Closing this, since I made a proof of concept and noticed that the api looks different than what I expected and this doesn't need support from as deep in wlroots as I expected.

from wlroots.