4 ms·
The problem I'm seeing is not that the author did something un-ethical (there are plenty black hats out there with no such concerns), but that the content can m
by ddalex 8y ago
The problem I'm seeing is not that the author did something un-ethical (there are plenty black hats out there with no such concerns), but that the content can modify the browser chrome behaviors, and that the users trust the browser chrome a lot more than the content (as it should).
As a workaround, I recommend using separate Firefox containers for big sites, as the big sites are the main attack surface of a lot of people. I.e. Firefox containers for Google, Facebook, Microsoft. This attack would be stopped by using a Google container as the back button will not work once you step out of the container to go to the result page.
Sure, it won't help you on a targeted attack, but will help a lot with this kind of drag-net attack.
- lysium 8y agoI don’t think your proposed workaround would help. The user stays on the malicious domain. Unless your container is clearly marked visually, only the url shows the savvy user that something is off.