Introducing s2n, a New Open-Source TLS Implementation
blogs.aws.amazon.com
Introducing s2n, a New Open-Source TLS Implementation
1–10 of 104 posts
Re: Introducing s2n, a New Open-Source TLS Implementation
#2Re: Introducing s2n, a New Open-Source TLS Implementation
#3Re: Introducing s2n, a New Open-Source TLS Implementation
#4[deleted]
Re: Introducing s2n, a New Open-Source TLS Implementation
#5My biggest issue with OpenSSL is that it also tries to do IO, but does it in a not too well-performing and non cross-platform way.
Re: Introducing s2n, a New Open-Source TLS Implementation
#6The fact that they are focusing on the TLS protocol itself and not the actual encryption implementation is a good way to start; the "extraneous complexity" is not really in algorithms like RSA/ECDSA/AES since those are specified mathematically, but in the handling of the protocol messages and states. That is also where most of the bugs tend to be.
It reminds me of this Hoare quote: "There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies."
Re: Introducing s2n, a New Open-Source TLS Implementation
#7Re: Introducing s2n, a New Open-Source TLS Implementation
#8Re: Introducing s2n, a New Open-Source TLS Implementation
#9Re: Introducing s2n, a New Open-Source TLS Implementation
#10Anyone else think this was a contraction of the a11y, i18n, a16z or f6s variety?