1728470 - Reenable Wayland socket

Status: RESOLVED FIXED

(Firefox Build System :: General, enhancement)

Description

[Robert Mader [:rmader]]

Bug 1631193 reenabled the X11 socket on Wayland and disabled the Wayland socket as the Wayland backend is not the default yet. While giving access to the X11 socket by default was right, dropping the Wayland socket makes testing it unnecessarily complicated and provides negligible security benefits - Wayland, in contrast to X11, is designed to be save. This is also reflected in Flatpak: while for X11 there is the fallback-x11 option, the same is not exposed for Wayland.

Thus lets enable the Wayland socket again, in order so make testing easier, helping making the Wayland the default sooner, which then is an actual security benefit.

Comment 1

[Robert Mader [:rmader]]

Attachment: Bug 1728470 - Reenable Wayland socket, r=mtabara

Bug 1631193 / D71448 reenabled the X11 socket on Wayland and disabled
the Wayland socket as the Wayland backend is not the default yet.
While giving access to the X11 socket by default was right,
dropping the Wayland socket makes testing it unnecessarily
complicated and provides negligible security benefits - Wayland,
in contrast to X11, is designed to be save. This is also reflected
in Flatpak: while for X11 there is the fallback-x11 option,
the same is not exposed for Wayland.

Thus lets enable the Wayland socket again, in order so make testing
easier, helping making the Wayland backend the default sooner, which
then is an actual security benefit.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/5901fd3cc5db
Reenable Wayland socket, r=emilio

Comment 3

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/5901fd3cc5db