I’ve discovered this once on my own, I had a complex control remapper and that I had been evolving into a horrific bash hydra of hacks over many years. I briefly tried to get it working when I switched to Wayland. I don’t remember which component broke me, but it went something like this:
“Hey, I wonder why doesn’t this thing work in Wayland. I wonder if I can whip up a pale imitation.” 10 minutes of stack overflow searches later…
“Oh… oh no.”
“I tried to keylog myself and the system doesn’t support keylogging.” is a frustrating situation. Because it’s neat from a security perspective and absolutely maddening from basically every other one.
It’s my own system and I’m root of it, if I want to run a program that inspects every bit of thing, including keylog myself I should be perfectly able to do it.
This kind of limitations are fake security, because Wayland is as secure as the rest of the stack it lies on top, it can’t add any more security than what Linux itself can guarantee. So yes, I can still read dev input and keylog myself anyway, it’s just more frustrating.
I have been using OSX since it was born because it was an amazing UNIX system and a convenient user environment. I moved back to Linux as my daily driven when they started introducing a tons of blockers to whatever I wanted to do “for security reasons”.
“Oh you want to debug your own software?”
“Nah, I can’t allow you to trace state of another process, I don’t care you are root”
and so on…
I’ve discovered this once on my own, I had a complex control remapper and that I had been evolving into a horrific bash hydra of hacks over many years. I briefly tried to get it working when I switched to Wayland. I don’t remember which component broke me, but it went something like this:
“Hey, I wonder why doesn’t this thing work in Wayland. I wonder if I can whip up a pale imitation.”
10 minutes of stack overflow searches later…
“Oh… oh no.”
“I tried to keylog myself and the system doesn’t support keylogging.” is a frustrating situation. Because it’s neat from a security perspective and absolutely maddening from basically every other one.
Not sure that’s a good thing.
It’s my own system and I’m root of it, if I want to run a program that inspects every bit of thing, including keylog myself I should be perfectly able to do it.
This kind of limitations are fake security, because Wayland is as secure as the rest of the stack it lies on top, it can’t add any more security than what Linux itself can guarantee. So yes, I can still read dev input and keylog myself anyway, it’s just more frustrating.
I have been using OSX since it was born because it was an amazing UNIX system and a convenient user environment. I moved back to Linux as my daily driven when they started introducing a tons of blockers to whatever I wanted to do “for security reasons”. “Oh you want to debug your own software?” “Nah, I can’t allow you to trace state of another process, I don’t care you are root” and so on…