How Android moved from C/C++ to Rust, and the real numbers
Step by step: how Android adopted Rust (Soong build, bindgen/cxx/AIDL interop, firmware, training), with architecture diagrams and real numbers.
Memory safety: moving from C/C++ to Rust, hardening C++, memory bugs and Rust security tooling. · 9 articles
Step by step: how Android adopted Rust (Soong build, bindgen/cxx/AIDL interop, firmware, training), with architecture diagrams and real numbers.
The bindings-and-abstractions architecture, where Rust already runs (Android, Binder) and lessons from the kernel's first Rust CVE.
Bounds checks in the C++ standard library: fast/extensive/debug modes, how to enable them, the rollout path and real numbers from Google.
BackupRefPtr keeps a hidden reference count, then quarantines and poisons freed memory with dangling pointers. Real costs and lessons for legacy C++.
Rust is memory-safe, but malicious crates still get in. The RustSec, cargo-deny and cargo-vet toolkit and how to wire it into CI.
Miri detects undefined behaviour while running tests, cargo-fuzz generates crashing inputs. How to put both in CI for unsafe and FFI code.
Data from Microsoft, Chromium and Android, the common memory bugs (buffer overflows, use-after-free…) and why careful coding or sandboxing isn't enough.
Ownership, borrowing and lifetimes; other safeguards; Android data (~1000× lower memory vulnerability density) and the limits of unsafe Rust.
Android's lesson: vulnerabilities cluster in new code, so write new code in Rust; a 4-step roadmap, the CISA/NSA framework, cxx/FFI and AI translation.
Try another keyword or clear the topic filter.
Follow binhAI via RSS (Feedly, Inoreader, Slack…) to get new articles as soon as they’re published.