Filippo Valsorda

> Even the noise created by these detected vulnerabilities has an effect on the overall security of people using it, as it can reduce the contrast for real issues. I...

This project is still maintained. I monitor issues, and would respond promptly to security reports or any breakage that makes mkcert not work anymore for its current users. Issues and...

Can we get some benchmarks and numbers for the performance improvement? My patch linked above might be a good starting point. It's a lot of complexity and it would have...

Keys should generally not be reused for both ECDH and ECDSA. It _can_ be safe, but it's not something we want to encourage blindly. crypto/ecdsa to crypto/ecdh exists because crypto/x509...

@ThadThompson yeah I think there's a good argument for uncompressed point to `*ecdsa.PublicKey` parsing, to replace the deprecated `elliptic.Unmarshal`. I'll repurpose this proposal. > If there was a function to...

The proposed parsing API is ``` package crypto/ecdsa // UnmarshalPublicKey parses a public key encoded as an uncompressed point // according to SEC 1, Version 2.0, Section 2.3.3 (also known...

I looked into Web Push a bit further, to figure out if the private key raw encoding is necessary, and I don't think it is. RFC 8292, Section 3.2 does...

A tagged release would also be useful for moving the version in Homebrew off v0.6.0 which is two years old and doesn't build with Go 1.16 anymore (because it was...

By TLS extension you mean TLS itself?

Hi all, thank you for working on this. Just wanted to mention that Avo support is pretty critical for us on the cryptography side. We've found Avo generators much easier...