WhatsApp migrated 160,000 lines of C++ to Rust to eliminate memory-safety bugs. Here’s how compiler-level security changed its threat model.
More details here: https://ostechnix.com/why-whatsapp-migrated-to-rust-from-c/
WhatsApp migrated 160,000 lines of C++ to Rust to eliminate memory-safety bugs. Here’s how compiler-level security changed its threat model.
More details here: https://ostechnix.com/why-whatsapp-migrated-to-rust-from-c/
"Rust is much more type safe than C is. And so if you have a void pointer, what does that mean in Rust? There's no translation for it. And that's how TrapC is fundamentally different because it actually remembers what that void pointer actually is."
https://www.theregister.com/2026/01/26/trapc_claude_c_memory_safe_robin_rowe/
This week on #OpenSourceSecurity I chat with @djc and @ctz about #Rustls. A lot has happened with Rustls in the last few years (and there's a lot more to come). Writing a TLS implementation is incredibly complicated, even when you don't have to worry about memory safety
https://opensourcesecurity.io/2025/2025-12-rustls-dirkjan-joe/

Josh talk to Dirkjan and Joe about Rustls (pronounced rustles), a Rust-based TLS library. Dirkjan and Joe are developers on Rustls. We talk about the history that got us to this point. The many many challenges in writing a TLS library (Rust or not). We also chat about some of what’s to come. Rustls has an OpenSSL compatibility layer which makes is a really interesting project. Episode Links Dirkjan Joe Rustls This episode is also available as a podcast, search for “Open Source Security” on your favorite podcast player.
The joint statement “Improving Europe's cybersecurity posture through memory safety”, has now been published: https://trifectatech.org/blog/calling-for-memory-safety-incentives-in-eu-cybersecurity-policies/
It calls for stronger #MemorySafety incentives in EU cybersecurity policies.
It is endorsed by industry leaders like Infineon Technologies, and industry and academic experts, including experts from Signify, Volvo Cars, Radboud University and Delft University of Technology.
We look forward to presenting it to national and EU policymakers in 2026.
Are you using std::ranges in your C++ code? If not, what is stopping you?
Ranges introduced a huge paradigm shift in the way we can write our C++ code. They can make the code way shorter, way better separated, and what's best - way more resilient to both logical and memory-related bugs. 🐞
If you haven't yet dabbled in ranges yourself, I've prepared a kind of cheatsheet reference article exploring many everyday use cases and how they can be improved by using the std::ranges library. 📏
You can read the article for free on my Medium:
➤ https://medium.com/@nerudaj/you-need-to-start-using-c-s-ranges-cf80c9f38602
What are your experiences with this library? Tell me in the comments 👇
"#Exclaves land in MacOS
Nobody is really surprised that the MacOS 26.0.1 firmware image of the about to be released MacBook Pro #M5 reveals that Memory Integrity Enforcement (#MIE) on top of the ARM64 Enhanced Memory Tagging Extension (#EMTE) is used. Extremely surprising is however that Apple is now shipping the Secure Kernel (#SK) and #ExclaveCore / #ExclaveOS with MacOS. This means Apple's newest security boundary #Exclaves has finally arrived in MacOS."