3 ms·
The main codebase... of a video sharing site. With no SLAs, and (at the time) no partner video-hosting agreements. The most awful thing that could happen to 20
by derefr 8y ago
The main codebase... of a video sharing site. With no SLAs, and (at the time) no partner video-hosting agreements.
The most awful thing that could happen to 2006-era YouTube: they could stop delivering ad impressions for an hour or two. Oh wait, no; 2006-era YouTube didn't even have ads yet.
- jrochkind1 8y agoI suppose more awful thing could be an accidental XSS or other vulnerability.
- darawk 8y agoWhich would then compromise what? People's youtube accounts?
- 0xDEFC0DE 8y agoIE6 had plenty of nasty vulns by the time this banner had gone up (06/14/2009): https://www.cvedetails.com/vulnerability-list/vendor_id-26/product_id-124/version_id-8371/Microsoft-IE-6.0.html https://www.cvedetails.com/vulnerability-list/vendor_id-26/p... That said, the people with this access probably knew WTF they were doing.
- darawk 8y agoExactly. They were getting rid of IE6
- chris_wot 8y agoAs opposed to the denial of service style bugs like an empty src element in an img tag?
- ljm 8y agoThey're perfectly capable of introducing other DOS bugs that don't depend on bad markup.
- dgoldstein0 8y agoThis is a poor argument - just because we can shoot our own feet, doesn't mean we should not try to prevent it from happening by accident. And it sounds like it wasn't just DOS - also just plain "it doesn't work in ie6" seems the most likely outcome; crashes and DOS that the article describes just sounds like the most egregious cases.