Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
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.
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
Everyone knows. There’s nothing to “find out”.
KWin is written in C++ but yes, it's not a "safe" language.
With at least three mainstream implementations – KWin, Mutter, and wlroots – it's highly unlikely that all would ever be equally affected by one bug.
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.