This is a bunch of nonsense. ekr was, for many years, the chair of the TLS working group at the IETF. He worked on TLS for years, which is why you'll see his na

This is a bunch of nonsense. ekr was, for many years, the chair of the TLS working group at the IETF. He worked on TLS for years, which is why you'll see his name on the RFCs for TLS 1.1[1] and 1.2[2]. He's currently doing the bulk of the work on TLS 1.3. The only hint of an insinuation that he's ever acted against the common interest comes from the fact that his name is also on the Extended Random draft. That's because the supposedly good half of the NSA (the Information Assurance Directorate) asked for that change and needed someone to guide the process through the IETF. Since ekr was so central to the working group and so practiced at it, he ended up writing it as a draft and thus his name got attached. I bet he seriously regrets that now but, at the time, there was no hint that this was bad. Sure, it was odd, but it was totally plausible that some government process had decreed that some minimum amount of entropy must be included or something so, whatever. Nobody planned to implement it and nobody really cared. In hindsight, that was naïve—on the part of everyone. But casting aspersions on ekr because of it is just codswallop. [1] https://www.ietf.org/rfc/rfc4346.txt https://www.ietf.org/rfc/rfc4346.txt [2] https://www.ietf.org/rfc/rfc5246.txt https://www.ietf.org/rfc/rfc5246.txt