The Wandering Shop

Tweede golfThe success story of the memory-safe sudo-rs, the Rust implementation of the sudo command, in an article from Prossimo, where it all began: <a href="https://www.memorysafety.org/blog/sudo-rs-headed-to-ubuntu/" rel="nofollow noopener" translate="no" target="_blank">https://www.memorysafety.org/blog/sudo-rs-headed-to-ubuntu/</a> We started work on sudo-rs in 2022, with <a href="https://social.ferrous-systems.com/@ferrous" class="u-url mention" rel="nofollow noopener" target="_blank">@ferrous</a>, for <a href="https://infosec.exchange/@ProssimoISRG" class="u-url mention" rel="nofollow noopener" target="_blank">@ProssimoISRG</a>. In 2024, sudo-rs moved to <a href="https://fosstodon.org/@trifectatech" class="u-url mention" rel="nofollow noopener" target="_blank">@trifectatech</a>. We're still working on it: maintenance, improvements, and readying for various distributions, of which Ubuntu 25.10 is the biggest milestone so far! 🥳 <a href="https://fosstodon.org/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a> <a href="https://fosstodon.org/tags/memorysafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#memorysafety</a> <a href="https://fosstodon.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a>

CHERI AllianceOne of our founding directors, Mike Eftimakis, sat down with Akshaya Asokan from Information Security Media Group (ISMG) to explore how CHERI is helping tackle one of cybersecurity’s biggest challenges: memory safety.CHERI (Capability Hardware Enhanced RISC Instructions) is a hardware-based approach to security, designed to prevent around 70% of today’s common vulnerabilities. Backed by industry leaders and the UK government, we're working to ensure global adoption across the electronics supply chain.Watch the interview to learn more about:💠 How CHERI addresses memory safety issues 💠 Common hardware supply chain vulnerabilities 💠 Progress on adoption by chipmakers 💠 Scalability challenges associated with CHERI🎥 Watch the full interview: <a href="https://www.bankinfosecurity.com/uks-cheri-alliance-expands-to-global-hardware-supply-chain-a-28942" rel="nofollow noopener" translate="no" target="_blank">https://www.bankinfosecurity.com/uks-cheri-alliance-expands-to-global-hardware-supply-chain-a-28942</a><a href="https://infosec.exchange/tags/CHERI" class="mention hashtag" rel="nofollow noopener" target="_blank">#CHERI</a> <a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurity</a> <a href="https://infosec.exchange/tags/HardwareSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#HardwareSecurity</a> <a href="https://infosec.exchange/tags/MemorySafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#MemorySafety</a> <a href="https://infosec.exchange/tags/SecurityByDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecurityByDesign</a> <a href="https://infosec.exchange/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a>

CHERI AllianceThe CHERI Alliance is all about bringing the computing world together to adopt CHERI security technology.We’re a mix of industry partners, open-source contributors, researchers, and governments, all working to make CHERI more accessible and widely used.Check out who’s already on board: <a href="https://cheri-alliance.org/member/" rel="nofollow noopener" translate="no" target="_blank">https://cheri-alliance.org/member/</a>We’ve got active working groups tackling everything from software porting to system integration and standards - all helping the community adopt and build with CHERI more effectively. Take a look: <a href="https://cheri-alliance.org/who-we-are/working-groups/" rel="nofollow noopener" translate="no" target="_blank">https://cheri-alliance.org/who-we-are/working-groups/</a>Curious? Keen to get involved? Here’s how to join us: <a href="https://cheri-alliance.org/memberships/" rel="nofollow noopener" translate="no" target="_blank">https://cheri-alliance.org/memberships/</a><a href="https://infosec.exchange/tags/CHERI" class="mention hashtag" rel="nofollow noopener" target="_blank">#CHERI</a> <a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurity</a> <a href="https://infosec.exchange/tags/MemorySafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#MemorySafety</a> <a href="https://infosec.exchange/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a>

David Chisnall (*Now with 50% more sarcasm!*)The <a href="https://infosec.exchange/@cheri_alliance" class="u-url mention" rel="nofollow noopener" target="_blank">@cheri_alliance</a> has around a thousand followers on LinkedIn and just joined the Fediverse today. Let’s see how quickly we can get them to more than that here!<a href="https://infosec.exchange/tags/CHERI" class="mention hashtag" rel="nofollow noopener" target="_blank">#CHERI</a> <a href="https://infosec.exchange/tags/MemorySafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#MemorySafety</a> <a href="https://infosec.exchange/tags/HardwareSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#HardwareSecurity</a> <a href="https://infosec.exchange/tags/FollowFriday" class="mention hashtag" rel="nofollow noopener" target="_blank">#FollowFriday</a>

CHERI Alliance👋 Hey infosec.exchange! We’re the CHERI Alliance — excited to join the community!🔐 We’re all about CHERI (Capability Hardware Enhanced RISC Instructions) — a powerful hardware-based approach to making memory safety and software security actually enforceable, by design.💡 CHERI helps stop things like buffer overflows and use-after-free bugs before they cause trouble — with hardware-enforced protections built right into the architecture.We’re here to: - Share news about the CHERI community in general - Talk about what our members are building with CHERI - Connect with folks who care about deep, meaningful security improvements Check us out 👉 cherialliance.orgGive us a follow if this sounds like your kind of thing!<a href="https://infosec.exchange/tags/CHERI" class="mention hashtag" rel="nofollow noopener" target="_blank">#CHERI</a> <a href="https://infosec.exchange/tags/MemorySafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#MemorySafety</a> <a href="https://infosec.exchange/tags/SecureByDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecureByDesign</a> <a href="https://infosec.exchange/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurity</a> <a href="https://infosec.exchange/tags/HardwareSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#HardwareSecurity</a>

Max RenkeDay 1 of posting to social media until I get an offensive security research jobFirst, I’m going to start with what I know – Windows. I need to recreate what I had access to at Microsoft, so that starts by setting up a dev environment and finding a copy of Windows System Internals, perhaps the greatest resource for learning Windows out there. My expertise is in Windows and virtualization, so I’m going to make sure I master those areas.Next, I don’t think I want to grind coding exercises, but I do need to shake the rust off my coding skills. I think I’m going to start with some HackTheBox challenges and find some CTFs to participate in. Finally, my long overdue goal: learn Rust. I’m not sure if this will help immediately, as I could choose to improve my knowledge of Python. But Rust was getting more and more popular in the areas of Windows I was tasked with protecting, so I need to learn what all the fuss is about with regards to memory safety. If anyone is on a similar journey, let’s hold each other accountable in the comments! I will be sure to document any write-ups at blog.maxrenke.com (work in progress).<a href="https://infosec.exchange/tags/OffensiveSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#OffensiveSecurity</a> <a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurity</a> <a href="https://infosec.exchange/tags/WindowsInternals" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsInternals</a> <a href="https://infosec.exchange/tags/HackTheBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackTheBox</a> <a href="https://infosec.exchange/tags/CTF" class="mention hashtag" rel="nofollow noopener" target="_blank">#CTF</a> <a href="https://infosec.exchange/tags/EthicalHacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#EthicalHacking</a> <a href="https://infosec.exchange/tags/RedTeam" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedTeam</a> <a href="https://infosec.exchange/tags/BlueTeam" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlueTeam</a> <a href="https://infosec.exchange/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a> <a href="https://infosec.exchange/tags/PythonProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#PythonProgramming</a> <a href="https://infosec.exchange/tags/DevEnvironment" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevEnvironment</a> <a href="https://infosec.exchange/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://infosec.exchange/tags/CyberCareer" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberCareer</a> <a href="https://infosec.exchange/tags/SecurityResearch" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecurityResearch</a> <a href="https://infosec.exchange/tags/MemorySafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#MemorySafety</a> <a href="https://infosec.exchange/tags/CyberCommunity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberCommunity</a> <a href="https://infosec.exchange/tags/JobSearch" class="mention hashtag" rel="nofollow noopener" target="_blank">#JobSearch</a> <a href="https://infosec.exchange/tags/TechJourney" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechJourney</a> <a href="https://infosec.exchange/tags/SecurityEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecurityEngineering</a> <a href="https://infosec.exchange/tags/Pentesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pentesting</a> <a href="https://infosec.exchange/tags/LearningEveryDay" class="mention hashtag" rel="nofollow noopener" target="_blank">#LearningEveryDay</a>

Sovereign Tech AgencyMemory-related bugs form the majority of impactful vulnerabilities, and eliminating them requires that all stakeholders, from government to industry to academia and technical communities do their part. As follow up, we’re working towards a second meeting to get more organizations, developers, and users of memory-safe and secure technologies on-board. Please reach out if you’re interested in participating in the next workshop. Thanks to everyone who joined us!<a href="https://mastodon.social/tags/MemorySafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#MemorySafety</a>(2/2)

CamdonI don't know who needs to hear this but if you bounds-check your user input and panic with a message that says "buffer overflow" and no other information you have achieved some minimal form of <a href="https://infosec.exchange/tags/memorysafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#memorysafety</a> but you're still a jerk

Kevin Karhan :verified:<a href="https://java.duke.social/users/naomi" class="u-url mention" rel="nofollow noopener" target="_blank">@naomi</a> <a href="https://infosec.space/tags/JVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#JVM</a> in <a href="https://infosec.space/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a>, when?<a href="https://infosec.space/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#Java</a> <a href="https://infosec.space/tags/MemirySafe" class="mention hashtag" rel="nofollow noopener" target="_blank">#MemirySafe</a> <a href="https://infosec.space/tags/MemorySafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#MemorySafety</a> <a href="https://infosec.space/tags/ProgrammingLanguages" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProgrammingLanguages</a> <a href="https://infosec.space/tags/Meme" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meme</a> <a href="https://infosec.space/tags/Memes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Memes</a>

David Chisnall (*Now with 50% more sarcasm!*)I have lost count of the number of people at Embedded World who have asked me ’what is memory safety?'If anyone is wondering how embedded security is going...<a href="https://infosec.exchange/tags/EmbeddedWorld" class="mention hashtag" rel="nofollow noopener" target="_blank">#EmbeddedWorld</a> <a href="https://infosec.exchange/tags/MemorySafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#MemorySafety</a> <a href="https://infosec.exchange/tags/CHERI" class="mention hashtag" rel="nofollow noopener" target="_blank">#CHERI</a>

Recent searches

Search options

Administered by:

Server stats:

#memorysafety