Filippo Valsorda

> This change will affect only TLS server certificates issued from the Root CAs preinstalled with iOS, iPadOS, macOS, watchOS, and tvOS. Do you have evidence of this affecting mkcert?

It is not! I will clean this up along with the rest of the docs soon. It would be interesting to have a conversation around licensing. I kinda wish we...

> And if we will go with only one reference implementation - there are far more suitable languages than Java for it! E.g. Rust or possibly Swift - but Rust...

@sophieschmieg happy to do the leg work of reformatting these in a Wycheproof format as promised if you can update them to the final FIPS :) I *think* we can't...

The existence of an "original" variant of ChaCha20Poly1305 and an IETF variant is unfortunate, but nearly everything and everyone converged on the IETF variant, and I wouldn't want to contribute...

> As long as crypto/ssh/cipher.go interoperates with OpenSSH and _does not import crypto/internal_ then fine. x/crypto/ssh may move to the standard library, at which point who knows what it will...

I'm a little surprised I didn't check in the Dockerfile, but the tool and version are here https://github.com/FiloSottile/edwards25519/blob/a7dfd8e4e6b456f2f0d11f0176885421029b6e3f/scalar.go#L28-L54

You need to update to a recent version of Go.

I am glad the codebase is being useful in learning! I am not sure what change you are suggesting, can you give me a rough example?

Nice! Always nice getting pure Go optimizations. Since these are parts of the library that track upstream, would you consider mailing them as Go CLs? If not, have you signed...