- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Lol not even reading it because I’ve always assumed that if there’s an RCE on desktop it will inevitably lead to full system compromise.
😅
It’s trust all the way down.
I love the link thumbnail!
Is this news worthy? X is the classic example of how a code base becomes completely unmanageable
I know Phoronix comments, but what’s up with the Linux Mint hate?
Tbf, there’s 1 Mint comment and 1 reply to that comment.
By providing a modified bitmap to the X.Org Server, a heap-based buffer overflow privilege escalation can occur.
Maybe we should stop writing security critical software in memory unsafe languages. I now this vulnerability was introduced a long time ago, but given that major Wayland compositors are still written in C, something like this isn’t too unlikely to happen again.
Let’s re-write all currently existing software in Rust, then there will be no more security holes, and every computer will be safe forever.
The problem is a huge codebase that no one understands.
Wait till bro find out the program written in the “memory safe language” depends on many libraries written in C
major Wayland compositors are still written in C
KWin is written in C++ but yes, it’s not a “safe” language.
something like this isn’t too unlikely to happen again.
With at least three mainstream implementations – KWin, Mutter, and wlroots – it’s highly unlikely that all would ever be equally affected by one bug.
