SpywareBlaster 6.0 released! - (Microsoft Edge, Brave, Vivaldi, Windows 10, and more!)

But doesn't this only apply to Internet Explorer? I don't think that Chromium based browsers and Firefox care about the registry keys that were mentioned. A browser like Chrome or Vivaldi can already block third party cookies, plus they are protected by Google Safe Browsing, plus you can install extenions like Ghostery and uBlock to block ads and tracking.

 

SpywareBlaster currently configures Chrome / Vivaldi / etc to block cookies from specific domains, and scripts from specific domains / patterns.

While you can see this configuration in Chrome settings, Vivaldi does not (currently) display Group Policy configuration visibly in its settings pages. Vivaldi does, however, apply it. (This method is distinct from how certain browser extensions work, and should work fine alongside them.)

 

Thank You @javacool- This end runs and is browser powered by Vivaldi. Useful information
-Nice longevity w/SpywareBlaster

 

+1 Must be the oldest / longest running program I have (especially now that I got it to work again, post #34)!

 

OK thanks, perhaps you already mentioned it, but now I finally understand how SB blocks scripts and cookies. So it uses Group Policy, cool but like I said before if you're already using the stuff that I mentioned I don't see much value in it. But for people who don't use that stuff, SB may still be useful.

 

What is blocked and how it is blocked matters (and differs), and defense-in-depth is a powerful security strategy.

There is great merit to multiple layers of protection, especially ones that function so differently (and potentially target different things).

 

Even if it's redundant, SpywareBlaster is another layer in case you need to disable uBlock or w/e, and possible bug/failure/etc. Even if the protection is minimal, it basically uses no system resources and only take seconds of your time to maintain.

I have a question though: Is 2020-07-29 the latest database? Did the update schedule change from end of the month every month? Thanks.

 

Hi,
Yes, at the moment the latest database update is from 29 July 2020.

 

Hi,

Please check for updates again.

 

Yes, I guess this is true. It's a bit similar to using the hostfile as a protection tool as done by Spybot Anti-Beacon.

 

In version 6, seem to be missing the Help file (sbhelp.chm)

 

See https://www.wilderssecurity.com/threads/spywareblaster-database-update-30-nov-2020.434725/

 

The requested URL cannot be provided

https://www.brightfort.com/downloads.htm<...>

Blocked by Web Anti-Virus

Reason: dangerous URL

Detection method: Cloud Protection

 

That one was also blocked by Kaspersky Security Cloud. On the first one Kaspersky was the only one that flagged it as Malware on Virus Total. The second one was not flagged by Kaspersky on Virus Total.

 

When I posted the update in the Update Alerts forum here there was no problem with going to the two links I posted (I always check that using IE11).
I checked the first link there posted about an hour ago, and I got indeed now a problem. But I checked again some 15 minutes ago, and no more problem.

Some more info about https://www.brightfort.com/spywareblaster.html
(checked within the last hour or so):

SSL Labs:
https://www.ssllabs.com/ssltest/analyze.html?d=www.brightfort.com

SSLShopper:
https://www.sslshopper.com/ssl-checker.html#hostname=https://www.brightfort.com/spywareblaster.html

Scanned at VT:
Only Kaspersky gave a warning.
(I did let VT re-analyse again)

 

@Dragon1952

Hi, did you already updated to SpywareBlaster version 6.0 ? Just asking because I see in your sig that you are still using 5.5
But maybe you haven't yet updated your sig

Cheers!

 

I have been on SB V6 since the day it was released. I forgot to change my sig.

 

Dragon1952, the last user of Spywareblaster these days ...

 

No I'm the last user!

 

No, that title belongs to me.

 

Or me.

 

I've submitted a false-positive report to Kaspersky - hopefully they fix it shortly.

 

Just updated. CoinIMP, CoinMining, and following scripts are not working/applying for Chrome.