Immunizing Chrome

[CliffT]

How do I do this?
Chrome 4.0.249.89
Spybot 1.6.2.46:

[TwistedMike]

you cant there is currently no immunization capabilities built into chrome.

[CliffT]

Thanks, any idea if this will change?

[spybotsandra]

Hello,

Chrome has no mechanisms for immunization, but there will be a plugin for live-blocking in Spybot 2.0.

Best regards
Sandra
Team Spybot

[Guardian666]

Hello,

Chrome has no mechanisms for immunization, but there will be a plugin for live-blocking in Spybot 2.0.

Best regards
Sandra
Team Spybot

Agreed, it doesn't have a real API and that's why NoScript has not been able to be ported for it, but for the purposes of SSD, the site blocking framework should be a sufficient exploit that can be used, no?

[lewisje]

Now that AdBlock for Chrome can block content, perhaps Spybot's immunization will be able to use whatever AdBlock for Chrome uses...

[Guardian666]

Now that AdBlock for Chrome can block content, perhaps Spybot's immunization will be able to use whatever AdBlock for Chrome uses...

No it can't because Adblock uses a CSS exploit to simply hide the items. It cannot block them and it certainly doesn't do it all the time, consistently or effectively, it just hides them. There is no real API outside of the blocking framework that is currently part of its core. That's why it might work for SSD because of the list system but not for anything meaningful like NoScript. ABP for Chrome is nothing more than an element hider using CSS hide, that's all.

[lewisje]

No it can't because Adblock uses a CSS exploit to simply hide the items. It cannot block them and it certainly doesn't do it all the time, consistently or effectively, it just hides them. There is no real API outside of the blocking framework that is currently part of its core. That's why it might work for SSD because of the list system but not for anything meaningful like NoScript. ABP for Chrome is nothing more than an element hider using CSS hide, that's all.

That used to be true but it's not true anymore:

Google Chrome now includes the ability to completely block resources from loading inside the browser, and the latest incarnation of the AdBlock extension for Chrome is using this "beforeload" event to not only hide ads from the user but prevent them from downloading entirely.

This brings the Chrome AdBlock extension in line with its namesake, the popular AdBlock Plus add-on for Firefox.

The Chrome extension — available here — is maintained by independent developer Michael Gundlach, and although the two share a name, it's not related to the popular AdBlock Plus Firefox add-on from coder Wladimir Palant. But as of last month, they also share the ability to block an ad before it downloads.

Google opened up Chrome to extensions in December, but until recently, the AdBlock extension could merely hide ads — not block them. "Firefox has always had support for blocking resources from downloading," Gundlach tells The Reg. "But when Chrome extensions came out, they lacked that ability, so they weren't as powerful as Firefox was. We've been having to hide the ads after downloading them or add CSS rules that say 'don't show these ads' even though they're downloading."

It's unclear when the "beforeload" event was added to Chrome — in part because it wasn't added by Google. Apple added it to the open source WebKit engine used by Chrome, and at some point, it made its way into the Google browser. It's now available in the latest stable version of Chrome, version 5. "Thank Apple," says Googler Aaron Boodman, the man who created the Firefox Greasemonkey extension, in an online discussion recently dug up by a Slashdot reader. "They added it to WebKit. We just inherited it."

http://www.theregister.co.uk/2010/07...urce_blocking/

Also, as I have said elsewhere, Safari on Windows includes the same ability to block content from loading.