Firefox 75 on Wayland now to have full WebGL, working VA-API acceleration

Re:Firefox 75 on Wayland now to have full WebGL, working VA-... by zlynx on Tuesday March 03, 2020 @06:43PM (#22479849)

> things like:

> screen sharing:

- Security problem, untrusted access to display, explicitly denied by design.

> hotkey daemons

- Security problem, untrusted input, denied by design.

> window managers

- Messing about with windows without authorization, denied by design.

> xdotools

- Untrusted input.

> clipboard managers

- Untrusted access to clipboard.

Either the compositor application has to do it, or it has to delegate it to a trusted application.

So yeah, deep philosophical problems. If you wanted Wayland to work exactly like X11 it won't because that is explicitly against its security design.

[ Parent | on HN ]

Re:Firefox 75 on Wayland now to have full WebGL, working VA-... by DCKing on Wednesday March 04, 2020 @02:05AM (#22481767)

All these security arguments are pure figments of your imagination. They are not based in reality at all.

Wayland is trying to do less than X11. The things you mention are not solved at the display protocol level on any platform but X11. Your security strawman never comes in to play.

[ Parent | on HN ]

Re:Firefox 75 on Wayland now to have full WebGL, working VA-... by AnIdiotOnTheNet on Wednesday March 04, 2020 @09:11AM (#22483868)

> Security problem

Yeah, it's not like anyone needs that functionality to do work or anything. In fact, why not just refuse to boot the computer in the first place? That'll stop a lot of security problems.

[ Parent | on HN ]