wayland-keylogger VS dwl

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.

Patching autostart:

If any of you have attempted to use SteamVR with DWL then you probably ran into the same issue I did. It doesn't have support for DRM leasing, so it can't actually show an image on the headset.

DWL

Have you checked DWL which is DWM for Wayland? I haven't tried it yet so I can't say anything more.

There's a python script called stacki3 that works both on i3wm and sway. There is also a dwm clone for wayland called dwl.

I currently use dwl which is much, much lighter than i3 and suits my needs. On my laptop I just don't have a window manager of any kind installed, I can get by with lynx and the TTY.

I wanted to try two wayland compositors out (specifically dwl and river) and cannot for the life of me seem to get it working properly. I am currently doing this inside a VirtualBox vm.

[0] https://github.com/djpohly/dwl