it seems only natural to have chacha20, if we have djb's other crypto suites. http://cr.yp.to/chacha.html http://tools.ietf.org/html/draft-agl-tls-chacha20poly1305-01 http://undeadly.org/cgi?action=article&sid=20131204090217
i believe it happens at all, it must first be landed in the go.crypto sub-repository before migrating to the main tree. besides, poly1305 is still in the go.crypto tree. I think probably opening up crypto/tls to accept external cipher suite implementations is the correct way to go (similar to the crypto.Hash interface)
Is this still on the table?
I assume this can be closed?
@leonklingele, yup, thanks.
This landed in Go 1.8: https://beta.golang.org/doc/go1.8#crypto_tls
And also in: https://godoc.org/golang.org/x/crypto/chacha20poly1305
Most helpful comment
@leonklingele, yup, thanks.
This landed in Go 1.8: https://beta.golang.org/doc/go1.8#crypto_tls
And also in: https://godoc.org/golang.org/x/crypto/chacha20poly1305