wayland-keylogger VS arewewaylandyet

Intercepting inputs meant for other apps is easy and it's already been done via LD_PRELOAD.

And all of this just for supposedly better "security", that can easily circumvented with trivial attacks.

Not in the same sense that there's a keylogger included with Windows, no. It's that it's easier to do on Xorg as opposed to Wayland. This isn't to say that it's impossible, however.

You can have keylogger on Wayland also without root priviledge. It's trivial: https://github.com/Aishou/wayland-keylogger

> you can still deliver different experiences at runtime — but you’re not likely to have the superuser privileges needed to run a leylogger or read ~/.ssh/id_rsa, etc, at that point.

Keyloggers are trivial to do in userspace Linux via LD_PRELOAD attacks[0], and typically your user account has permission to read ~/.ssh/id_rsa.

[0] https://github.com/Aishou/wayland-keylogger

I have read that bare Linux is totally insecure (https://github.com/Aishou/wayland-keylogger) unless you use some means of sandboxing. That's why I have been reading a lot about firejail, AppArmor, Tomoyo, etc.

It's tracked in an issue here with a label things that wayland do not support

Create tool! I like the style it provides. I recommend to add it to [AreWeWaylandYet](https://arewewaylandyet.com/)

https://arewewaylandyet.com/

We are still not Wayland yet. And my setup is personally blocked by both Xs.

Of course, you'll have to find replacements for some X programs, I recommend you visit https://arewewaylandyet.com/ and take a look. :D

I've found https://arewewaylandyet.com/ and https://wayland.app/ (but the latter appears limited).

https://arewewaylandyet.com doesn't tell the whole story, but it's a good place to start.