Search Results
7/10/2025, 4:57:14 PM
>>105856975
Why do you think they're pushing so hard for Wayland?
If you stop for one second and think, Wayland's security model makes no sense. Oh, so program A can't see what program B does? Why does that matter? The Red Hat employee posing as an open source volunteer will say that it prevents keyloggers, but the thing is that a user that has a keylogger running is running malware. A user that is already running malware is fucked anyway. Malware without root on GNU/Linux can easily modify bashrc to download and execute scripts, to capture the root password and use that to escalate privileges to run arbitrary code, read/write on ~/, etc.
The only problem that Wayland solves is that GNOME devs can watch CP on their program of choice and no other program in the computer can read the contents of that screen. Just mount an encrypted volume or use an encrypted connection and nobody can monitor it.
That's what Wayland is for.
Why do you think they're pushing so hard for Wayland?
If you stop for one second and think, Wayland's security model makes no sense. Oh, so program A can't see what program B does? Why does that matter? The Red Hat employee posing as an open source volunteer will say that it prevents keyloggers, but the thing is that a user that has a keylogger running is running malware. A user that is already running malware is fucked anyway. Malware without root on GNU/Linux can easily modify bashrc to download and execute scripts, to capture the root password and use that to escalate privileges to run arbitrary code, read/write on ~/, etc.
The only problem that Wayland solves is that GNOME devs can watch CP on their program of choice and no other program in the computer can read the contents of that screen. Just mount an encrypted volume or use an encrypted connection and nobody can monitor it.
That's what Wayland is for.
Page 1