Linux

11523 readers

274 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

108

Wayland didn’t kill Linux desktops, but it did expose their weakest assumptions [EDIT: Warning, article likely written with AI assistance] (www.xda-developers.com)

submitted 3 days ago* (last edited 2 days ago) by ProdigalFrog@slrpnk.net to c/linux@programming.dev

77 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] bisby@lemmy.world 17 points 3 days ago (1 children)

"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.

[–] amol@piefed.social 13 points 3 days ago

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...