Last month, we announced the addition of post-quantum key exchange support to our Rustls TLS library! While no PQ adversary exists today, we're preparing for the future now. Learn more: buff.ly/3xbWDiS

Can memory safe languages eliminate 70% of security bugs? Short answer, YES. Find out how in this recent post by Jennifer Goforth Gregory on the Security Intelligence IBM Security blog: buff.ly/4cKvWlr

REPOST: buff.ly/4cM3EY6
How it started vs. how it's going buff.ly/3P9VLBk

Check out this explanation of the memory safe language Rust by Serdar Yegulalp (Serdar Yegulalp) in their @infoworld article: buff.ly/4aDzDYh

#MemorySafety : Because eliminating memory safety bugs helps make the Internet safer and more secure. 🔐

Great to see the positive implications orgs are experiencing as they consider transitioning to memory safe languages like #Rustlang . Read all about it in this post by Thomas Claburn from The Register: buff.ly/3VH7KdU

🤝 Connections forged at Tectonics are powering real change! Like the collaboration between Tweede golf - @[email protected] and Immunant Inc.. Learn more: buff.ly/49eXJYn #MemorySafety

Buffer overflows, use-after-free, and other memory safety issues have no place in our digital future. Our goal is to eliminate these vulnerabilities by moving the Internet's security-sensitive software infrastructure to memory safe code. Learn more: buff.ly/3FZ6GcJ

#ICYMI
We recently added post-quantum key exchange support to our Rustls TLS library! Get the full scoop here: buff.ly/3xbWDiS

📈 Benchmarking by @Adolfo Ochagavía helps ensure Rustls stays on track to outperform OpenSSL. Stay tuned for more insights! #MemorySafety #Rustls
buff.ly/3RIOMQp

We've added experimental post-quantum key exchange support to the Rustls TLS library, safeguarding TLS connections against potential future post-quantum adversaries. Learn more in our recent blog post!👇 buff.ly/3xbWDiS

🤔 Why are we building a memory safe AV1 decoder? This is why.👇 #MemorySafety
buff.ly/3VuDdzL