My point is that disabling domain fronting (or leaving it disabled after finding the bug's root cause) was a policy decision, not something necessary to mitigate the bug or prevent it from re-occurring.
Filippo: You, sadly, fall in the later camp and have for some time. You’re wrong here. You’re wrong most times you post uninformed speculation. It’s tiresome.
I wish you luck in whatever you’re doing post-Google and hope you find the success you’ve desired since our first conversation that will, I pray, stop you from your latent and seemingly unpatchable personality bug of making shit up and making yourself a more important figure in every story than you actually are or ever have been.
If you'd please review and follow the site guidelines, we'd appreciate it: https://news.ycombinator.com/newsguidelines.html.
To be clear, that's not correct we did do this to mitigate the bug.
We were facing the bug that I described (the cross stream thing) showing up when Lantern was used. It was causing disruption to our service and customers were writing in. We were trying to understand what was happening and needed to stop it. One of the things we did to stop it was disable domain fronting. As we were seeing the customer reports we didn't know if this was an OpenSSL bug, something in NGINX, something in our code, but we did know that Lantern was somehow causing it and they were doing domain fronting which wasn't the standard use of our service and so we dropped it.