4 ms·
If the attacker wasn't stupid, it would double it. If he has an exploit for chrome, he is going to add the magic tag and let ChromeFrame render the code thus t
by tomjen2 17y ago
If the attacker wasn't stupid, it would double it.
If he has an exploit for chrome, he is going to add the magic tag and let ChromeFrame render the code thus the browser is vulnerable.
If he has an exploit for IE, he isn't going to add the magic tag, IE's engine is going to handle the rendering and the browser is vulnerable.
The key is that the attacker can choose what browser the victim is using, thus he can target either browser.
- aarongough 17y agoAh, I hadn't realized that the individual website had control over whether Chrome Frame was used or not... That is a terrible idea. If the user elects to install Chrome Frame it should render every page except for exceptions set at the user's discretion. I absolutely agree. Letting the website choose is just adding attack vectors.
- enomar 17y agoIt also ensures that sites that only work in IE continue to work. Google Frame simply lets someone visit sites that only work in IE and sites that need HTML5 without having to know which browser to use for which site. Having the site control when GF is used is essential for this to work.
- aarongough 17y agoI understand the reasoning behind that, but ultimately it should be the user not the website that has control over whether Chrome Frame is activated or not. A user can always visit an IE-only website in FireFox, so it's not creating a new problem there. Allowing the user control, rather than the website, means the user will get the benefit of Chrome Frame by default rather than as the exception and will stop a potential attacker from getting to choose their attack vector...