The weird thing is they got @matthew_d_green to front it for themhttps://twitter.com/RichFelker/status/888842483668586500 …
-
-
Replying to @letoams @matthew_d_green
Not familiar with his role in this but my guess would be it was ~= what the linked article called the "practical"/compromise position.
1 reply 0 retweets 0 likes -
If that's not the case could you elaborate rather than just making an accusation of "fronting"?
2 replies 0 retweets 0 likes -
Replying to @RichFelker @matthew_d_green
fronting as "his name is on the draft and he was at IETF for the first time I remember promoting it at TLS"
1 reply 0 retweets 0 likes -
Replying to @letoams @matthew_d_green
Again that doesn't really distinguish without looking at mailing list posts or meeting minutes, etc..
1 reply 0 retweets 0 likes -
IIRC he was one target of the "NSA is bribing academics" smear campaign, so I'm (hopefully understandably) skeptical of related claims...
2 replies 0 retweets 0 likes -
Replying to @RichFelker @matthew_d_green
enterprise client modification seems the obvious solution - and also prevents non-enterprise abuse
1 reply 0 retweets 0 likes -
Replying to @letoams @matthew_d_green
I agree with your 100%. Malicious enterprise features belong 100% in the enterprise endpoints.
1 reply 0 retweets 0 likes
I've long advocated for removing custom root CA support from stock browsers and selling special "enterprise" versions that are MITM'able.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.