#memorysafety — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #memorysafety, aggregated by home.social.
-
If you want to understand how CHERI works and the relationship between memory safety and compartmentalisation, and why starting from a programmer model is essential if you want to build useful hardware, here you go!
-
If you want to understand how CHERI works and the relationship between memory safety and compartmentalisation, and why starting from a programmer model is essential if you want to build useful hardware, here you go!
-
Fil-C: Garbage In, Memory Safety Out! - Filip Pizlo | SSW 2026
“Fil-C is a fanatically compatible memory-safe implementation of C and C++. Lots of software compiles and runs with Fil-C with zero or minimal changes.”
https://www.youtube.com/watch?v=5F-2Y1LPRek&feature=youtu.be
-
Fil-C: Garbage In, Memory Safety Out! - Filip Pizlo | SSW 2026
“Fil-C is a fanatically compatible memory-safe implementation of C and C++. Lots of software compiles and runs with Fil-C with zero or minimal changes.”
https://www.youtube.com/watch?v=5F-2Y1LPRek&feature=youtu.be
-
Ah, yet another thrilling piece where "Memory Safety" reigns supreme! 🚀 Spoiler alert: it's not just about Rust! 🤯 Apparently, this riveting manifesto dares to suggest that caring about software safety might not be a secret Rust cult. #Groundbreaking. 💥
https://itsallaboutthebit.com/memory-safety-absolutists/ #MemorySafety #RustSoftware #SoftwareSafety #TechTrends #HackerNews #ngated -
Ah, yet another thrilling piece where "Memory Safety" reigns supreme! 🚀 Spoiler alert: it's not just about Rust! 🤯 Apparently, this riveting manifesto dares to suggest that caring about software safety might not be a secret Rust cult. #Groundbreaking. 💥
https://itsallaboutthebit.com/memory-safety-absolutists/ #MemorySafety #RustSoftware #SoftwareSafety #TechTrends #HackerNews #ngated -
🐢 Watch as Filip Pizlo valiantly attempts to trade memory safety for a steaming pile of Fil-C garbage. 🎥 Dive into a riveting YouTube video where technical jargon meets copyright text soup. 🍜 Spoiler: No garbage collectors were harmed in the making of this masterpiece. 🗑️
https://www.youtube.com/watch?v=5F-2Y1LPRek #FilipPizlo #MemorySafety #YouTubeVideo #TechJargon #CopyrightSoup #NoGarbageCollectors #HackerNews #ngated -
🐢 Watch as Filip Pizlo valiantly attempts to trade memory safety for a steaming pile of Fil-C garbage. 🎥 Dive into a riveting YouTube video where technical jargon meets copyright text soup. 🍜 Spoiler: No garbage collectors were harmed in the making of this masterpiece. 🗑️
https://www.youtube.com/watch?v=5F-2Y1LPRek #FilipPizlo #MemorySafety #YouTubeVideo #TechJargon #CopyrightSoup #NoGarbageCollectors #HackerNews #ngated -
🦀 In a new post on the QNX Everywhere Blog, Jonathan Pallant of Ferrous Systems shares the story behind building a GUI application in Rust on QNX and how Rust's lifetime annotations helped us build a safe wrapper around the QNX Screen Graphics Subsystem, preventing use-after-free bugs with no runtime overhead.
🔗 Read the blog: https://qnx.software/en/blog/2026/using-rust-to-avoid-use-after-free-bugs
-
🦀 In a new post on the QNX Everywhere Blog, Jonathan Pallant of Ferrous Systems shares the story behind building a GUI application in Rust on QNX and how Rust's lifetime annotations helped us build a safe wrapper around the QNX Screen Graphics Subsystem, preventing use-after-free bugs with no runtime overhead.
🔗 Read the blog: https://qnx.software/en/blog/2026/using-rust-to-avoid-use-after-free-bugs
-
An interesting, early preview of memory safety in Carbon and the migration of unsafe C++ code to safe Carbon code (via Chandler Carruth):
https://hachyderm.io/@chandlerc/116898796409614862
#Carbon #CPlusPlus #CPP #Rust #MemorySafety #Porting #Programming #PLDI
-
An interesting, early preview of memory safety in Carbon and the migration of unsafe C++ code to safe Carbon code (via Chandler Carruth):
https://hachyderm.io/@chandlerc/116898796409614862
#Carbon #CPlusPlus #CPP #Rust #MemorySafety #Porting #Programming #PLDI
-
Memory Safe Context Switching (longjmp, setjmp) in Fil-C
https://fil-c.org/context_switches
#HackerNews #MemorySafety #ContextSwitching #FilC #longjmp #setjmp
-
Memory Safe Context Switching (longjmp, setjmp) in Fil-C
https://fil-c.org/context_switches
#HackerNews #MemorySafety #ContextSwitching #FilC #longjmp #setjmp
-
Apple rewrote their C-based TrueType hinting interpreter in memory-safe Swift for the Fall 2025 releases. Not only did they kill a major security attack surface, they landed 13% faster using Swift 6 features like ~𝐶𝑜𝑝𝑦𝑎𝑏𝑙𝑒 and 𝑆𝑝𝑎𝑛.
🔗: https://www.swift.org/blog/migrating-truetype-hinting-to-swift/ by Scott Perry (@numist)
-
Oh, look! Another riveting blog post dissecting the glaringly obvious: #Rust doesn't serve memory safety CVEs on a silver platter like C/C++. 🎉 We all needed a 2026 update on how not to write exploit-prone code, because that's as timeless as memes from 2010. 🍾🤦♂️
https://kobzol.github.io/rust/2026/06/15/how-memory-safety-cves-differ-between-rust-and-c-cpp.html #MemorySafety #CPlusPlus #ExploitPrevention #CodingBestPractices #BlogPost #Humor #HackerNews #ngated -
Oh, look! Another riveting blog post dissecting the glaringly obvious: #Rust doesn't serve memory safety CVEs on a silver platter like C/C++. 🎉 We all needed a 2026 update on how not to write exploit-prone code, because that's as timeless as memes from 2010. 🍾🤦♂️
https://kobzol.github.io/rust/2026/06/15/how-memory-safety-cves-differ-between-rust-and-c-cpp.html #MemorySafety #CPlusPlus #ExploitPrevention #CodingBestPractices #BlogPost #Humor #HackerNews #ngated -
Memory safety CVEs differ between Rust and C/C++
https://kobzol.github.io/rust/2026/06/15/how-memory-safety-cves-differ-between-rust-and-c-cpp.html
-
Memory safety CVEs differ between Rust and C/C++
https://kobzol.github.io/rust/2026/06/15/how-memory-safety-cves-differ-between-rust-and-c-cpp.html
-
depthfirst’s AI agent found 21 FFmpeg zero-days (MEDIUM, CVE-2026-39210 – 39218), mainly heap/stack overflows — oldest since 2003. No active exploitation. Patches rolling out. Update ASAP. https://radar.offseq.com/threat/depthfirsts-ai-agent-found-21-ffmpeg-zero-days-cve-99cb219d #OffSeq #FFmpeg #AI #MemorySafety
-
depthfirst’s AI agent found 21 FFmpeg zero-days (MEDIUM, CVE-2026-39210 – 39218), mainly heap/stack overflows — oldest since 2003. No active exploitation. Patches rolling out. Update ASAP. https://radar.offseq.com/threat/depthfirsts-ai-agent-found-21-ffmpeg-zero-days-cve-99cb219d #OffSeq #FFmpeg #AI #MemorySafety
-
Cool:
“The Fil-C Optimized Calling Convention”, Filip Pizlo (https://fil-c.org/calling_convention).
On HN: https://news.ycombinator.com/item?id=48162876
On Lobsters: https://lobste.rs/s/5mnt43/fil_c_optimized_calling_convention
#C #Compilers #Programming #FilC #MemorySafety #Capabilities #CallingConvention #ABI #Optimization #Efficiency #Speed
-
Cool:
“The Fil-C Optimized Calling Convention”, Filip Pizlo (https://fil-c.org/calling_convention).
On HN: https://news.ycombinator.com/item?id=48162876
On Lobsters: https://lobste.rs/s/5mnt43/fil_c_optimized_calling_convention
#C #Compilers #Programming #FilC #MemorySafety #Capabilities #CallingConvention #ABI #Optimization #Efficiency #Speed
-
Memory safety, reliability, and performance are key reasons why Rust continues to gain momentum in software development, especially in safety-critical areas. KDAB will be at Oxidize 2026 in Berlin this September to engage with Rust professionals and discuss the future of safe systems programming.
More details: https://www.kdab.com/kdab-at-oxidize-2026-berlin-september-1416/
#MemorySafety #Performance #SoftwareDevelopment #RustLang #Oxidize2026
-
Memory safety, reliability, and performance are key reasons why Rust continues to gain momentum in software development, especially in safety-critical areas. KDAB will be at Oxidize 2026 in Berlin this September to engage with Rust professionals and discuss the future of safe systems programming.
More details: https://www.kdab.com/kdab-at-oxidize-2026-berlin-september-1416/
#MemorySafety #Performance #SoftwareDevelopment #RustLang #Oxidize2026
-
The #PyConUS #Security Track fires back up after lunch! See you at 1:45PM in Room 103ABC where Python core developer Emma Smith (@emmatyping) will be talking about “Rust and CPython”.
Don't miss it!! 🦀🐍
-
The #PyConUS #Security Track fires back up after lunch! See you at 1:45PM in Room 103ABC where Python core developer Emma Smith (@emmatyping) will be talking about “Rust and CPython”.
Don't miss it!! 🦀🐍
-
Bitcoin Core Exposes High-Severity Memory Safety Flaw
Bitcoin Core developers have disclosed a high-severity vulnerability, tracked as CVE-2024-52911, which is the project's first known memory safety flaw that could potentially allow remote code execution. This rare but critical bug was fixed months ago and affects Bitcoin Core releases from 2017 to early 2025.
#MemorySafety #BitcoinCore #Cve202452911 #Vulnerability #RemoteCodeExecution
-
Warning: CVE-2025-40739 (CWEs: ['CWE-125']) found no CAPEC relationships.
Warning: CVE-2025-40741 (CWEs: ['CWE-121']) found no CAPEC relationships. -
Ah yes, the thrilling world of #FilC, where we simplify a "memory safe" version of C by rewriting everything with the grace of a toddler with finger paints. 🎨💻 Because nothing says #innovation like rehashing old concepts with more buzzwords than a Silicon Valley power lunch. 🚀
https://www.corsix.org/content/simplified-model-of-fil-c #MemorySafety #CProgramming #TechBuzz #HackerNews #ngated -
Google Bolsters Pixel Security with Rust-Based DNS Parser Integration
Google is taking a significant step to supercharge Pixel device security by integrating a Rust-based DNS parser into the modem firmware of the Pixel 10, leveraging the power of memory-safe code to fortify its software stack. This strategic move underscores the company's commitment to bolstering device security from the ground up.
