Hacker News new | past | comments | ask | show | jobs | submit login

Thanks for the report. We, Google, are currently working to add support for other ciphers. (I was going to file a bug, until I noticed there was already one with work underway).



Assuming you actually represent google, can you link to the bug, or paste bin if your bug tracker isn't publicly accessible?

I'm curious to know what was the basis of this configuration decision. It seems like someone went out of their way to hamstring your encryption. Possibly someone benchmarked every combination and disabled all but the fastest. Wouldn't something like this go through a security review before hitting prod?


Sorry, this is an internal bug tracker, so I am not allowed to share any detail.


I tried to find a normal channel to report this and came up empty. In the future, how does on alert google to issues like this?


In that case, a Youtube issue, go to https://www.youtube.com/t/contact_us, click "Current Site Issues", and follow the instructions.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: