#memorysafety — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #memorysafety, aggregated by home.social.
-
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!! 🦀🐍
-
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!! 🦀🐍
-
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
-
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. -
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 -
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 -
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 -
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 -
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.
-
Google reveals Pixel 10 modem firmware now uses Rust to reduce baseband security risks
https://fed.brid.gy/r/https://nerds.xyz/2026/04/pixel-10-rust-baseband/
-
Google reveals Pixel 10 modem firmware now uses Rust to reduce baseband security risks
https://fed.brid.gy/r/https://nerds.xyz/2026/04/pixel-10-rust-baseband/
-
I am able to tolerate rules/discipline when I'm given a good reason for them. And I put higher emphasis on avoiding harming others than myself.
I wish the #Rust book and other sources explained the why of the borrow checker and not just the how. Particularly from a security perspective rather than just a preventing mistakes perspective, because see above. I want to be able to make my own mistakes, but my users deserve secure software.
-
I am able to tolerate rules/discipline when I'm given a good reason for them. And I put higher emphasis on avoiding harming others than myself.
I wish the #Rust book and other sources explained the why of the borrow checker and not just the how. Particularly from a security perspective rather than just a preventing mistakes perspective, because see above. I want to be able to make my own mistakes, but my users deserve secure software.
-
📰 図を描いて理解するRustの所有権 (👍 41)
🇬🇧 Visual guide to understanding Rust's ownership system using diagrams and chemistry analogies (H₂ + O₂ → H₂O) to explain memory safety concepts.
🇰🇷 다이어그램과 화학 반응 비유를 활용하여 Rust의 소유권 시스템과 메모리 안전성 개념을 시각적으로 설명합니다.🔗 https://zenn.dev/northward/articles/rust-feeling-of-ownership
-
📰 図を描いて理解するRustの所有権 (👍 41)
🇬🇧 Visual guide to understanding Rust's ownership system using diagrams and chemistry analogies (H₂ + O₂ → H₂O) to explain memory safety concepts.
🇰🇷 다이어그램과 화학 반응 비유를 활용하여 Rust의 소유권 시스템과 메모리 안전성 개념을 시각적으로 설명합니다.🔗 https://zenn.dev/northward/articles/rust-feeling-of-ownership
-
People often claim that memory-safe languages eliminate the class of memory bugs, but that is not true and can give less experienced devs a false sense of security.
You can violate borrow checker at runtime in Rust with zero unsafe blocks. You can have null-pointer dereference in C#. You can index out of bounds in Java.
The difference is that while C++ will crash at unspecified time with SIGSEGV (or not crash at all), memory-safe languages will either crash at a well-defined time in a well-defined way, or they will emit an exception you shall handle.
In the customers eyes, that might not even be a difference.
-
People often claim that memory-safe languages eliminate the class of memory bugs, but that is not true and can give less experienced devs a false sense of security.
You can violate borrow checker at runtime in Rust with zero unsafe blocks. You can have null-pointer dereference in C#. You can index out of bounds in Java.
The difference is that while C++ will crash at unspecified time with SIGSEGV (or not crash at all), memory-safe languages will either crash at a well-defined time in a well-defined way, or they will emit an exception you shall handle.
In the customers eyes, that might not even be a difference.
-
People often claim that memory-safe languages eliminate the class of memory bugs, but that is not true and can give less experienced devs a false sense of security.
You can violate borrow checker at runtime in Rust with zero unsafe blocks. You can have null-pointer dereference in C#. You can index out of bounds in Java.
The difference is that while C++ will crash at unspecified time with SIGSEGV (or not crash at all), memory-safe languages will either crash at a well-defined time in a well-defined way, or they will emit an exception you shall handle.
In the customers eyes, that might not even be a difference.
-
People often claim that memory-safe languages eliminate the class of memory bugs, but that is not true and can give less experienced devs a false sense of security.
You can violate borrow checker at runtime in Rust with zero unsafe blocks. You can have null-pointer dereference in C#. You can index out of bounds in Java.
The difference is that while C++ will crash at unspecified time with SIGSEGV (or not crash at all), memory-safe languages will either crash at a well-defined time in a well-defined way, or they will emit an exception you shall handle.
In the customers eyes, that might not even be a difference.
-
People often claim that memory-safe languages eliminate the class of memory bugs, but that is not true and can give less experienced devs a false sense of security.
You can violate borrow checker at runtime in Rust with zero unsafe blocks. You can have null-pointer dereference in C#. You can index out of bounds in Java.
The difference is that while C++ will crash at unspecified time with SIGSEGV (or not crash at all), memory-safe languages will either crash at a well-defined time in a well-defined way, or they will emit an exception you shall handle.
In the customers eyes, that might not even be a difference.
-
Soon on github: rilua - a Rust port of Lua 5.1. Key upgrades:
✅ Arena-based GC with gen. indices - no memory corruption
✅ Result-based errors - no longjmp/setjmp risks
✅ AST compilation - testable, optimizable pipeline
✅ Trait-based API - ergonomic embeddingPasses 19/23 PUC-Rio tests. Sacrifices some speed (0.9-2.2x) for memory safety & maintainability.
-
Soon on github: rilua - a Rust port of Lua 5.1. Key upgrades:
✅ Arena-based GC with gen. indices - no memory corruption
✅ Result-based errors - no longjmp/setjmp risks
✅ AST compilation - testable, optimizable pipeline
✅ Trait-based API - ergonomic embeddingPasses 19/23 PUC-Rio tests. Sacrifices some speed (0.9-2.2x) for memory safety & maintainability.
-
Soon on github: rilua - a Rust port of Lua 5.1. Key upgrades:
✅ Arena-based GC with gen. indices - no memory corruption
✅ Result-based errors - no longjmp/setjmp risks
✅ AST compilation - testable, optimizable pipeline
✅ Trait-based API - ergonomic embeddingPasses 19/23 PUC-Rio tests. Sacrifices some speed (0.9-2.2x) for memory safety & maintainability.
-
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/
-
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/
-
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/
-
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 -
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 -
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 -
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 -
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 -
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 -
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/
-
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/
-
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/
-
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/
-
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/
