roland.zone

roland.zone

@roland.zone

go (the language) security team lead 🔥💻🔥

1.3K followers143 following132 posts

wrote a little about the (now old news) security events of last week

Go@golang.org

“Our Response To The eMudhra Key Disclosure Incident” by Roland Shoemaker, on behalf of the Go Security team — https://go.dev/blog/emudhra-incident #golang

roland.zone reposted

If you make HTTPS requests or have other TLS clients and care about MITM attacks, you need to update today. If you run Go: go get go@1.27.3 If you run Homebrew: brew update brew install ca-certificates If you run Linux, maybe stay off the internet for now.

Filippo Valsorda@filippo.abyssdomain.expert

🚨 Six WebPKI Intermediate CAs are compromised. This is bigger than Heartbleed, but a client-side issue. Anything that verifies certificates against public roots, like most TLS clients, is/was affected. Details, live test, patched versions and workarounds at emudhra.we-have-a-problem.com Act now.

allowing generation of one byte keys is actually a feature, it’s a differentiator that really sets my hsm company apart from everyone else

can someone just break ecc already so we can stop having this annoying fight on the ietf tls wg mailinglist

somewhat ironic that everyone is posting about how perelman is the only human to have solved a millennium prize problem when one of the main reasons he rejected the prize was because it ignored the work done by hamilton

i think all football shirts should be required, by law, to have a proper shirt collar. they just look better. thanks for coming to my ted talk

fifa collapsing the second it even looks in the direction of private equity is just... beautiful, a+ story writing, my compliments to the chef

excited to talk about the (mostly) boring vulns we have, with a slight digression about how LLMs have completely turned the way vulns are found upside down 🙃

GopherCon@gophercon.com

If Go is memory-safe, where do its vulnerabilities come from? 🔒 Go Security Team Lead @roland.zone shares how the Go team identifies, responds to, and learns from vulnerabilities across the Go ecosystem. Discover what those lessons mean for building more secure Go software. 🎟️ gophercon.com

roland.zone reposted

If Go is memory-safe, where do its vulnerabilities come from? 🔒 Go Security Team Lead @roland.zone shares how the Go team identifies, responds to, and learns from vulnerabilities across the Go ecosystem. Discover what those lessons mean for building more secure Go software. 🎟️ gophercon.com

i'm sorry, i have zero interesting in consuming a "companion podcast", i'd like to watch your slop tv show, derive my own opinions, and then immediately forget everything about it 30 minutes later

i have opinions about the ffmpeg security thing but i'm not going to post them, for my own sanity (but i am posting about not posting about it)

I recently passed my 5 year anniversary at Google on the Go team (thanks to them for reminding me), which also means it's been about 10 years since I first joined the Let's Encrypt team. It's been amazing to see the projects grow over those years, and I couldn't be prouder to have worked on them.

I don't think they post here, but excited to be talking about what the Go Security team does, and why (hopefully) you don't hear much about us, at GopherCon UK in August.

I tend not to do talks that often, I think the last one I did was at 32C3 about ten years ago in 2015 when I talked about launching Let's Encrypt!

roland.zone reposted

Here's something I am very excited about: Photosynthesis! 🌱☀️ A proposal to have CAs run transparency logs and make X.509 certificates out of Merkle Tree inclusion proofs. This is similar to how CT would have worked in an ideal world, and it solves the problem of PQC sizes in logs and handshakes.

mailarchive.ietf.org[TLS] Photosynthesis, an update to Merkle Tree CertificatesPhotosynthesis combines the Static CT API with the ideas in Merkle Tree Certificates.