1
Planning Go 1.20 cryptography work
My plans for Go 1.20 include landing the crypto/ecdh package, making progress on moving math/big out of the security perimeter, and a batch of crypto/tls work.
Filippo Valsorda
We now know how the seeds of the NIST elliptic curves were generated: they’re not the hash of some saucy sentence, but the output of drand48() seeded with the time, which was indeed in 1997–98.
- Popular posts
- 26
- Total points
- 6,821
- HN comments
- 2,464
- Rank
- #137 personal
Visit words.filippo.io → RSS feedOn Hacker News Jan 2022 – Oct 2026
Security & Privacy 20Programming Languages 5Software Engineering 4Open Source 4Math & Algorithms 4Tools & Productivity 3
2
Go 1.20 Cryptography
A lot of new cryptography is landing in Go 1.20, including the new crypto/ecdh package and math/big-less RSA and ECDSA backends!
3
Rustgo: Calling Rust from Go with near-zero overhead (2017)
Go has good support for calling into assembly, and a lot of the fast cryptographic code in the stdlib is carefully optimized assembly, bringing speedups of over 20 times.
4
Go.sum is not a lockfile
In Go, go.mod acts as both manifest and lockfile. There is never a reason to look at go.sum.
5
Go Cryptography State of the Union
I delivered my traditional Go Cryptography State of the Union talk at GopherCon US 2025 in New York. It goes into everything that happened at the intersection of Go and cryptography over the last year.