How is wayland going to be more secure than x11 when it replaces

Wayland, supported by systemD which is made by pottering.

Try again sweetie I'm not install that botnet

>>62320487
Unlike sysvinit, X11 needs to die

File: typical.png (3KB, 407x123px) Image search: [Google]

3KB, 407x123px

>>62320487

>>62320766
X11 is different, it's a bloated mess that even the devs admit is insecure and has patches over patches trying to make it modern. Sooner or later the devs will stop caring to update X11 and it won't be used anymore

>>62320487
>unironically using the word sweetie
Fucking neck your self faggot

It's "secure" and "simple" because it has no features (by design). Practically everything is supposed to be implemented in the compositor instead. You'll have Gnome doing their own thing, not giving a shit about anyone else. KDE will try to compromise as always but be a bit buggier and behind. There will be a few other hobby tier projects, mainly wlc/sway which seem to be the emergent "wm" option

So basically Red Hat/freedesktop crowd will consolidate even more power on their hands

>>62321026
Most of what X11 can do is done by the kernel and much of the rest should be done by the client. Now DEs will have to take responsibility for their projects rather than just relying on X11 to do it for them.

can't be worse

only way to make x11 secure is execute multiple x servers in vms and have them communicate via a custom interface through shared memory (qubesos)

X11 was so bloated it used to have its own print server, a fucking print server for a windowing system. It goes completely againt the philosphy of do one thing and do it well

>>62320457
mostly by not implementing the ridiculous amounts of cruft that X11 has gathered over the years.

This also means certain things you've certainly grown to expect to "just be there" won't actually be there anymore, in part due to security implications, and in part due to requiring implementation. Taking screenshots is a good example. Allowing one application to essentially have free access to the entire framebuffer whenever it wants is bad security practice, but something we've grown to expect.

>>62321132
Screenshot tools will still be possible, it will have to be done by the compositor rather than by another program

>>62321063
this

google's chromebook os did this running gentoo underneath and a single opengl surface

>>62321118
So lets have a compositor that does everything instead XD

Could someone explain a noob how display server can be insecure?

>>62320457
Can I run wayland with OpenRC?

>>62321193
You can either let the compositor do everything it is capable of doing or you have a gigantic bloated window system that can do everything to the point its an operating system

>>62320487
>>62320766
Wayland has literally nothing to do with systemd.

>>62321208
Yes.

>>62321197
In X, clients can basically do anything, including stealing keyboard input from other clients.