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/
#MemorySafety
"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/
Oh, joy! 🎉 Another ode to the almighty null pointer, where we learn that catching them is as easy as catching a cold in winter 🌨️. But wait, the "Billion Dollar Mistake" is just a misunderstood little rascal 🙄, because, really, who needs memory safety when you have "individualelement mindsets" to blame? 😂👨💻
https://www.gingerbill.org/article/2026/01/02/was-it-really-a-billion-dollar-mistake/ #nullpointer #billiondollarmistake #memorysafety #programminghumor #technews #HackerNews #ngated
Ah yes, the age-old quest for a Rust paradise without the meddling borrow checker—because clearly, who needs memory safety when you can live on the edge? 😂🔪 Why bother with the pesky details of secure coding when you can just throw caution to the wind and #YOLO your way through software development? 🙈💻
https://github.com/buyukakyuz/rustmm #RustParadise #MemorySafety #SoftwareDevelopment #CodingHumor #EdgeOfChaos #HackerNews #ngated
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/
Oh no! 🙈 The invincible #Rust code has been dethroned by a pesky #CVE #vulnerability in the Linux Kernel. 🚨 Guess the "memory-safe" bragging rights were too good to be true! 😂
https://www.phoronix.com/news/First-Linux-Rust-CVE #LinuxKernel #MemorySafety #TechNews #HackerNews #ngated
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."
The article is too verbose & the discussions flame out, but some good references in both:
“Memory Safety For Skeptics”, ACM Queue (https://queue.acm.org/detail.cfm?id=3773095).
Via HN: https://news.ycombinator.com/item?id=45879012
On Lobsters: https://lobste.rs/s/mytmnl/memory_safety_for_skeptics
💻 Weekend project: I finally got time to update the #MerlinOS presentation with the newest features.
Highlights:
* Source level debugging for ROM and flash images in MS VSCode
* UART debugging features that support source symbols, showing the module and line number in the source that triggered a panic
👇
https://paolozaino.wordpress.com/portfolio/merlin-a-modern-memory-safe-kernel-and-platform/#kernel-documentation
#OperatingSystem #KernelDevelopment #SystemsProgramming #EmbeddedSystems #MemorySafety #FormalVerification #OpenSource #SoftwareEngineering #LowLevelProgramming
"#Google has disclosed that the company's continued adoption of the #Rust programming language in #Android has resulted in the number of memory safety vulnerabilities falling below 20% of total vulnerabilities for the first time."
https://thehackernews.com/2025/11/rust-adoption-drives-android-memory.html
Rust continues to reshape Android’s security posture.
Google reports memory-safety bugs are now under 20%, backed by:
• 1000× reduction in memory-safety bug density vs C/C++
• 4× fewer rollbacks
• Faster reviews + fewer revisions
• Rust moving deeper into kernel, firmware & Android’s security-sensitive apps
A recent “near-miss” RCE (CVE-2025-48530) in unsafe Rust was mitigated by Scudo before reaching public release.
Thoughts from the AppSec community?
Follow @technadu for more unbiased cybersecurity reporting.
#RustLang #MemorySafety #AndroidSecurity #AppSec #InfoSec #DevSecOps #SecureCoding #TechNadu
Very impressive:
“InvisiCaps: The Fil-C Capability Model”, Filip Pizlo (https://fil-c.org/invisicaps).
See Also: “Fil's Unbelievable Garbage Collector”, Filip Pizlo (https://fil-c.org/fugc).
#C #FilC #MemorySafety #Programming #GarbageCollection #GC #InvisiCaps #FUGC
🧠💥 "Memory Safety for Skeptics" is here to convince you that worrying about your software's memory safety is just as thrilling as watching paint dry. 🎨😴 Despite #Rust being hailed as the knight in shining armor for this cause, it's really just a hipster language trying to make buffer overflows feel passé. 🛡️📉
https://queue.acm.org/detail.cfm?id=3773095 #MemorySafety #Skeptics #Programming #BufferOverflows #SoftwareDevelopment #HackerNews #ngated
Memory Safety for Skeptics
https://queue.acm.org/detail.cfm?id=3773095
#HackerNews #MemorySafety #Skeptics #Cybersecurity #SoftwareDevelopment #ACMQueue
“A Note On Fil-C”, Graydon Hoare (https://graydon2.dreamwidth.org/320265.html or https://web.archive.org/web/20251107034852/https://graydon2.dreamwidth.org/320265.html if it 403s 😒).
On Lobsters: https://lobste.rs/s/ywvatn/note_on_fil_c
On HN: https://news.ycombinator.com/item?id=45842494
#FilC #Rust #MemorySafety #Programming #C #ProgrammingLanguages
Ah, the mesmerizing world of FilC—a groundbreaking addition that promises to make your coding life safer than a padded room. 🤦♂️ Because, of course, what every developer dreams of is yet another layer of memory safety bureaucracy to babysit their already flawless code. 🎉
https://graydon2.dreamwidth.org/320265.html #FilC #MemorySafety #DeveloperExperience #CodingLife #TechNews #HackerNews #ngated
“Fil-C: A Memory-Safe C Implementation”, LWN (https://lwn.net/SubscriberLink/1042938/658ade3768dd4758/).
On HN: https://news.ycombinator.com/item?id=45735877
On Lobsters: https://lobste.rs/s/mg0aur/fil_c_memory_safe_c_implementation
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst