4 ms·
Yep, reading the Go source is what inspired me to do this, it's still very compact and readable. I originally used an AEAD cipher but found it was impossible t
by syncsynchalt 8y ago
Yep, reading the Go source is what inspired me to do this, it's still very compact and readable.
I originally used an AEAD cipher but found it was impossible to demonstrate on the command line (openssl enc refuses to do AEAD because it can't confirm the authentication in a streaming context).
A friend asked me to demonstrate ALPN in this but as I looked into it I found it was distracting, as there's already so much going on and any new feature required digression. Maybe next time!
As for 1.3 my next project was going to be implementing it rather than documenting it. Just a throwaway implementation, nothing you'd want to use.
- kodablah 8y ago> As for 1.3 my next project was going to be implementing it rather than documenting it. Just a throwaway implementation, nothing you'd want to use. Since you read the Go source, you might like [0]. I will say I personally think Go could have done better. I think it's too compact, too hidden, too disorganized, too underdocumented, and too inflexible/non-extensible. I began to pick some of it apart for a DTLS impl I started at [1], but have put on temporary hold yesterday due to other work obligations. 0 - https://github.com/cloudflare/tls-tris https://github.com/cloudflare/tls-tris 1 - https://github.com/cretz/go-dtls https://github.com/cretz/go-dtls
- syncsynchalt 8y agoI've also had https://github.com/h2o/picotls https://github.com/h2o/picotls suggested.
- syncsynchalt 8y agoLink to the go source: https://golang.org/src/crypto/tls/ https://golang.org/src/crypto/tls/