as i could see there was no option to place sites to block somewhere in google chrome, there was almost no options for anything special. no security options like disable active scripting or such either as i could see.

Scanning cookies and history will be easy, they're in SQLite tables very similar to Firefox 3. Blocking content for immunization is a bit more difficult, I agree, but there's already a place for it - just look at the files, not just the GUI ;) Safe Browsing is a database that seems to be intended for that purpose; just the content of the blob fields in there is a bit unclear yet.

Well this is the first beta after all, I do not think Google will ship a browser so devoid of security/safety features any time soon (heard that it does not support client ssl). Going by the way Gmail has been in beta for years I expect at least 6 months and 3 betas before the browser releases version 1.

As of now they have made the rendering engine and other basics part of the beta, they might bring in more details about cookie control, site blocking later.

I used Chrome for 3 days. Ran Spybot S&D and found 61 malware programs running. I'll be on the sidelines until immunization is figured out.

Don

I just don't like how Google Chrome sends user info to the Google server. Would there be a solution to this problem?

I've recently seen the first clone where the phoning has been stripped right in the source code. I think it was called Iron Chromium or something like that.

Recompiling the (open) source is obviously the best choice, since if there is no phoning home, none needs to get blocked. One just have to make sure sich a clone is always up-to-date to non have otherwise fixed bugs and holes open.

Has anything been done on Chrome support since 2008, when all the messages above were posted? I'm writing in February 2010, and Spybot still doesn't immunize for Chrome.

About Chrome Support, read these posts:
http://forums.spybot.info/showpost.p...59&postcount=4
http://forums.spybot.info/showpost.p...88&postcount=2

Google Analytics Opt-out Browser Add-on (BETA)
To provide website visitors with more choice about how their data is collected by Google Analytics, we have developed the Google Analytics Opt-out Browser Add-on. The add-on communicates with the Google Analytics JavaScript (ga.js) to indicate that information about the website visit should not be sent to Google Analytics.

If you want to opt out, download and install the add-on for your current web browser. The Google Analytics Opt-out Browser Add-on is available for Internet Explorer (versions 7 and 8), Google Chrome (4.x and higher), and Mozilla Firefox (3.5 and higher).


http://tools.google.com/dlpage/gaoptout

@peter51: immunization is still not possible.

But: Spybot 2.0 will have a Chrome plugin, which is ready and "just" waiting for the whole 2.0 package to be released.

very nice post.
i ahve accepted you post informations.

What is the estamated date that this release 2..0 will be ready?

We've been saying that we would release a 2.0 beta "something like next week" so often... :D Next monday, the guy responsible for the two new browser plugins will be back from vacation. I'll receive the latest version of them and pack them into the installer, which is already done except for that. I hope late next week.

I like chrome but still use ie8 because of immunization. I am curious about the plugin for live-blocking in Spybot 2.0. Is this going to be like ie8's immunization or is it completely something different?

Any news on availability of the immunization function of SpyBot for Google's Chrome browser? Thanks.

I came here to ask that now that Chrome has finally added the site blocking framework if it would be possible to add the immunizations to Chrome and Chrome variations like Dragon but I see that this has been discussed for a while and it has been promised in the next release.

So my question is when is this release coming? I know you said late next week in your post but it seems to have been more than that but still nothing, so wondering when we might see that? Also, will we need to reinstall the 2.0 as a new installation or will it get pushed through the update?

Also, you mentioned that it will be a plugin in Chrome (also assuming you are making it a plugin for Fx as well) but is there anyway to just embed them into the block lists like we do now with IE, Host, and Firefox so that an extension need not be installed and so there won't ever be the issue of discontinuity between the browser plugin versions and the core SSD version? Just wondering.

Thank you all for the great work and looking forward to seeing the 2.0 release, I have been waiting on it and looking forward to it for a while now :D

Yep, wondering about chrome and 2.0? I absolutely love chrome. Favorite browser ever, so any help here would be nice. =)

I would also like to know when 2.0 will come out. Can we get an update?

ok... is this forum inactive or being ignored? either one presents a problem to me.

i need help pleas