Skip to contentSkip to conversation

wayland.if etc

DISCUSSION Russell Coker 2 participants 2 messages Jul 25 – Jul 29

lore
Share & tools
lore
#0 lore raw

We have a wayland module in the policy. The file wayland.if has the following interfaces:
wayland_compositor_domain
wayland_compositor_tmpfs
wayland_client_domain
wayland_client_tmpfs
wayland_client_sandboxed_domain
wayland_stream_connect

Of those the only use is in docker.te with a single use of wayland_stream_connect().

Is it worth trying to make wayland.if actually useful or should we just keep doing it all in wm.if and remove wayland.*?

Signature · 2 lines
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/
#1 lore raw
Quoted 9 lines · Russell Coker

We have a wayland module in the policy. The file wayland.if has the following interfaces:
wayland_compositor_domain
wayland_compositor_tmpfs
wayland_client_domain
wayland_client_tmpfs
wayland_client_sandboxed_domain
wayland_stream_connect

Quoted 5 lines

Of those the only use is in docker.te with a single use of wayland_stream_connect().

Is it worth trying to make wayland.if actually useful or should we just keep doing it all in wm.if and remove wayland.*?

The purpose of the wayland module was to avoid starting with the baggage from the xserver module. Since Xorg seems to be slowly on the way out, I can see a future where the wayland module could be merged into other modules. However, for the time being, I think we should keep things clean.

I'm certainly open to additional thoughts.

Signature · 1 line
Chris PeBenito