#MemorySafety
👻 No ghost pointers here – Rust keeps our memory alive and safe.

Happy Halloween from the Ferrous Systems team! 🎃🦀

Do you like Ferris' costume?

#Rust #Ferrocene #MemorySafety
October 31, 2025 at 1:09 PM
Rolling my own, though a pretty thin layer on top of the `concread` and `leaky-bucket` crates: github.com/memorysafety...
Initial rate limiting impl based on the `leaky-bucket` and `concread` crates by jamesmunns · Pull Request #67 · memorysafety/river
github.com
August 29, 2024 at 3:05 PM
Trying to explain Rust's borrow checker. It's less 'memory safety,' more 'Gandalf shouting YOU SHALL NOT PASS at your pointers.' Makes you appreciate garbage collection... sometimes. #RustLang #DevLife #MemorySafety #CodingHumor
April 2, 2025 at 2:01 AM
I’ve been meaning to check out #PartialEvaluation (en.wikipedia.org/wiki/Partial...) & #FutamuraProjections for a while:

“Writing Truly Memory Safe JIT Compilers”, Mike Hearn (medium.com/graalvm/writ...).

Via HN: news.ycombinator.com/item?id=4060...

#Java #Interpreters #JIT #MemorySafety #GraalVM
Partial evaluation - Wikipedia
en.wikipedia.org
June 15, 2024 at 2:34 PM
Fil's Unbelievable Garbage Collector
fil-c.org
October 2, 2025 at 2:14 PM
Tara from Sovereign Tech Agency and Hugo will be hosting the next 'Memory Safety in the EU' meeting in Amsterdam, on Tue 26 Aug (during #OSSummit).

Read more here: tweedegolf.nl/en/blog/160/...

@hugovandepol.bsky.social
@tarakiyee.bsky.social
@sovereign.tech

#memorysafety #securitybydesign
Update on our advocacy for memory-safety - Blog - Tweede golf
We’ve been raising awareness of the importance of using memory-safe technology to build systems that are truly secure-by-design. We do this alongside our core business, which is to help companies ...
tweedegolf.nl
August 20, 2025 at 1:48 PM
Gotta check how a TrapC program integrates with existing C and C++ codebases. #C #C++ #Programming #MemorySafety #Tech
March 5, 2025 at 5:13 AM
“Mojo is inspired by Rust, but doesn’t aspire to be Rust” – paraphrasing Chris Lattner in this 👇🏽👌🏽 #video:

“Mojo🔥: A Deep Dive On Ownership With Chris Lattner”, Modular (youtu.be/9ag0fPMmYPQ?...).

Eagerly waiting for part 2.

#Mojo #Rust #Python #Compilers #PLDI #MemorySafety
Mojo🔥: a deep dive on ownership with Chris Lattner
Learn everything you need to know about ownership in Mojo, a deep dive with Modular CEO Chris LattnerIf you have any questions make sure to join our friendly...
youtu.be
June 1, 2024 at 2:35 AM
Memory safety is tough for shells handling complex data. The Oilshell author noted implementing GC for YSH to manage nested structures, unlike Bash/Awk which limit complexity to avoid GC needs. Rust helps, but complexity remains. #memorysafety 4/6
May 8, 2025 at 9:30 AM
medium.com/@simon.swart...

Started learning Rust - will be posting updates on Medium. If you aren't a medium member, and want to read the article, just send me a message and I'll get it to you.

#Rust #RustLang #LearnRust #BorrowChecker #CodeOwnership #MemorySafety #SystemsProgramming #BackendDev
Learning Rust — Part 1 — Ownership Basics (and our first Rust app)
Let’s learn Rust — the easy way!
medium.com
November 9, 2025 at 7:43 PM
Linux kernel maintainer advocates Rust adoption to eliminate common memory safety bugs in new code
https://lore.kernel.org/rust-for-linux/2025021954-flaccid-pucker-f7d9@gregkh/
#rust #linuxkernel #memorysafety #codemigration #development
February 20, 2025 at 12:01 AM
LOL .. an important set of principles no doubt but the timeline is ridiculous — never mind they took this long to even write such a thing! Do want to acknowledge and +1 their efforts #MemorySafety @cacm.acm.org
It Is Time to Standardize Principles and Practices for Software Memory Safety – Communications of the ACM
cacm.acm.org
February 14, 2025 at 11:01 AM
bmann (/bmann) starred memorysafety/river (/memorysafety/river) · September 1, 2024 13:54
memorysafety/river (/memorysafety/river)

This repository is the home of the River reverse proxy application, based on the pingora library from Cloudflare.

Rust 1.6k... https://github.com/memorysafety/river
September 1, 2024 at 1:57 PM
8/10 Languages like Rust are praised for their memory safety features, potentially preventing issues that plagued older C/C++ codebases. #RustLang #MemorySafety
April 26, 2025 at 8:34 AM
Interesting discussion:

“Is Ada Safer Than Rust?”, /r/ProgrammingLanguages (old.reddit.com/r/rust/comme...).

Via HN: news.ycombinator.com/item?id=3849...

#Ada #Rust #Programming #Safety #MemorySafety #PLDI #ProgrammingLanguages
Is Ada safer than Rust?
Posted in r/rust by u/we_are_mammals • 168 points and 138 comments
old.reddit.com
December 3, 2023 at 1:02 PM
Fil-C shines by bringing memory safety to *existing* C/C++ codebases without extensive rewrites. While Rust is great for new projects, Fil-C offers a pragmatic path to secure legacy systems, a critical need for many organizations. #MemorySafety 2/6
November 3, 2025 at 8:00 AM
Addressing #MemorySafety in critical infrastructure is a complex issue with multiple approaches. The Sovereign Tech Fund supports several initiatives, but technologist Tara Tarakiyee points out some limitations in a blog post: www.sovereigntechfund.de/news/on-rust...
On Rust, Memory Safety, and Open Source Infrastructure | Sovereign…
www.sovereigntechfund.de
May 22, 2024 at 10:19 AM
Aleph One's article "Smashing The Stack For Fun And Profit" appeared in Phrack on 1996-11-08. The 30th anniversary of that paper will be in 1142 days.

What can we do between now and then to show him that we're finally taking the matter seriously? #memorySafety #secureByDesign
September 22, 2023 at 12:55 PM
📣 New Podcast! "Apple's Leap in iOS Security: Unpacking Memory Integrity Enforcement (MIE)" on @Spreaker #apisecurity #applesecurity #approov #cybersecurity #devicesecurity #emte #ios #iphone #memorysafety #mie #mobilesecurity #pradeo
Apple's Leap in iOS Security: Unpacking Memory Integrity Enforcement (MIE)
In this episode, we're diving deep into Apple's groundbreaking Memory Integrity Enforcement (MIE), an unprecedented effort poised to redefine the landscape of mobile security, and we'll also explore the broader spectrum of threats targeting the iOS ecosystem. Apple's Memory Integrity Enforcement (MIE) is the culmination of a half-decade of intensive design and engineering, combining the unique strengths of Apple silicon hardware with advanced operating system security. Apple believes MIE represents the most significant upgrade to memory safety in the history of consumer operating systems. This comprehensive, always-on protection is designed to provide industry-first memory safety across Apple devices, all without compromising device performance. The Driving Force: Combating Mercenary Spyware While the iPhone has never experienced a successful, widespread malware attack, Apple's focus for MIE is primarily on the mercenary spyware and surveillance industry. These highly sophisticated threats, often associated with state actors, utilize exploit chains that can cost millions of dollars to target a small number of specific individuals. A common denominator in these advanced attacks, whether targeting iOS, Windows, or Android, is their reliance on memory safety vulnerabilities. MIE aims to disrupt these highly effective exploitation techniques that have been prevalent for the last 25 years. How MIE Works: A Three-Pronged Defense MIE is built on a robust foundation of hardware and software innovations: 1. Secure Memory Allocators: Apple's efforts in memory safety include developing with safe languages like Swift and deploying mitigations at scale. Key to MIE are its secure memory allocators, such as kalloc_type (introduced in iOS 15 for the kernel) and xzone malloc (for user-level in iOS 17), alongside WebKit's libpas. These allocators use type information to organize memory, thwarting attackers' goals of creating overlapping interpretations of memory to exploit use-after-free and out-of-bounds bugs. 2. Enhanced Memory Tagging Extension (EMTE): Building on Arm's 2019 Memory Tagging Extension (MTE) specification, Apple conducted deep evaluations and collaborated with Arm to address weaknesses, leading to the Enhanced Memory Tagging Extension (EMTE) specification in 2022. MIE rigorously implements EMTE in strictly synchronous, always-on mode, a crucial factor for real-time defensive measures in adversarial contexts. EMTE prevents common memory corruption types:     ◦ Buffer Overflows: The allocator tags neighboring allocations with different secrets. If memory access spills over into an adjacent allocation with a different tag, the hardware blocks it, and the operating system can terminate the process.     ◦ Use-After-Free Vulnerabilities: Memory is retagged when reused. If a request uses an older, invalid tag for retagged memory, the hardware blocks it. EMTE also specifies that accessing non-tagged memory from a tagged region requires knowing that region’s tag, making it harder for attackers to bypass EMTE. 3. Tag Confidentiality Enforcement: This critical component protects the implementation of Apple's secure allocators and the confidentiality of EMTE tags, even against side-channel and speculative-execution attacks. Apple's silicon implementation prevents tag values from influencing speculative execution, a vulnerability seen in other MTE implementations. Furthermore, MIE addresses Spectre variant 1 (V1), a speculative-execution vulnerability, with a mitigation designed for virtually zero CPU cost, making it impractical for attackers to leak tag values and guide attacks. Impact and Availability Memory Integrity Enforcement is built right into Apple hardware and software in all iPhone 17 and iPhone Air models, offering unparalleled, always-on memory safety protection for key attack surfaces, including the kernel and over 70 userland processes. Importantly, MIE was designed to deliver groundbreaking security with minimal performance impact, remaining completely invisible to users. Apple is also making EMTE available to all developers in Xcode as part of the new Enhanced Security feature. Extensive evaluations by Apple's offensive research team have confirmed that MIE dramatically reduces the exploitation strategies available to attackers, making it extremely difficult to rebuild exploit chains. Beyond MIE: Other Threats to iOS Devices While MIE targets memory corruption, the iOS ecosystem faces a range of other threats: • Application-Level Threats: These include various forms of malware, such as TouchID malware, Yispecter, and AceDeceiver, which exploit design flaws or trick users. More widespread are leaky applications (greyware), representing 61% of iOS apps, which legally collect and silently forward unnecessary personal data like location, contacts, and photos to third parties. • Network-Level Threats: iOS devices are as exposed to network-related threats as any other operating system. These include Man-In-The-Middle (MITM) attacks, where communications are intercepted or altered via unprotected WiFi hotspots or spoofing. Phishing and Smishing are the most detected network threats on mobile devices, trapping users through malicious links in emails or SMS. Rogue cell towers can also trick devices into connecting, allowing interception of calls, SMS, and data. • Device-Level Threats: OS vulnerability exploits occur when cybercriminals leverage public security holes in outdated iOS versions (e.g., Pegasus spyware). Jailbroken devices bypass iOS security checks, making them more vulnerable to malicious applications. Finally, unmanaged or malicious profiles can be configured to send all transiting data to external servers, crushing data privacy. Organizations like Pradeo offer solutions such as Mobile Threat Defense (MTD) and Mobile Application Security Testing to provide full protection for mobile fleets and applications, safeguarding data and ensuring compliance with data privacy regulations. -------------------------------------------------------------------------------- Relevant Links to Source Materials: • For deeper insights into Apple's Memory Integrity Enforcement, refer to the "Memory Integrity Enforcement: A complete vision for memory safety in Apple devices" research by Apple Security Engineering and Architecture (SEAR). • To understand broader iOS threats, consult the "iOS SECURITY REPORT: THREATS TARGETING APPLE MOBILE DEVICES" white paper by Pradeo. Sponsored by: Enhance your mobile API security with Approov. Visit them at https://www.google.com/url?sa=E&q=https%3A%2F%2Fapproov.io. -------------------------------------------------------------------------------- Keywords: Apple security, Memory Integrity Enforcement (MIE), iOS security, memory safety, mercenary spyware, EMTE, secure allocators, buffer overflows, use-after-free, speculative execution, cyber threats, mobile security, iPhone security, hardware security, software security, enterprise mobility, mobile malware, leaky applications, Man-In-The-Middle, phishing, jailbreaking, OS vulnerabilities, Pradeo Security, API security, mobile API protection, device integrity.
www.spreaker.com
September 14, 2025 at 9:01 PM
"You're not secure by design, if you're not memory safe!" Hugo van de Pol and Marc Schoolderman will present this talk at ONE Conference in The Hague on 1 Oct 2025.

buff.ly/nKw3uQ9

@hugovandepol.bsky.social

#cybersecurity #memorysafety
September 23, 2025 at 10:14 AM