Closed Bug 1728470 Opened 3 months ago Closed 3 months ago

Reenable Wayland socket

Categories

(Firefox Build System :: General, enhancement)

enhancement

Tracking

(firefox93 fixed)

RESOLVED FIXED
93 Branch
Tracking Status
firefox93 --- fixed

People

(Reporter: rmader, Assigned: rmader)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

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.

See Also: → 1631193

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.

Assignee: nobody → robert.mader
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch
You need to log in before you can comment on or make changes to this bug.