Spyware Blaster "Custom Blocking" Update 06/08/04

A slight tweak but a change all the same.
For those of you that are uncomfortable editing the file, disable
protection for the one item discussed.
http://forum.aumha.org/viewtopic.php?t=7106

Silj

--
siljaline

MS - MVP Windows (IE/OE) AH-VSOP
________________________________
Security Tools Updates
http://forum.aumha.org/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)

siljaline wrote:
A slight tweak but a change all the same.
For those of you that are uncomfortable editing the file, disable
protection for the one item discussed.
http://forum.aumha.org/viewtopic.php?t=7106

Silj

Hi, Silj,

I just noticed that if you disable the one item in the custom block list
after the update has been applied to SpywareBlaster, it also disables the
item in the main application. It's not immediately evident, but if you
close and then reopen SpywareBlaster, the status for IE will show one item
has protection disabled. It should work okay if the item is disabled in the
custom block list first, and then the update is applied to the main
application, since the CLSID is only written once to the registry. I
suspect though that even with this approach, the item will be renabled in
the custom block list when the protection is applied in the main
application. I'm not able to test it with the update already applied.

Anyway, to make a long story short, unless you edit the item from the custom
block list, it's probably better to just keep it enabled.

Tom

"TomV" wrote:
Hi, Silj,

I just noticed that if you disable the one item in the custom block list
after the update has been applied to SpywareBlaster, it also disables the
item in the main application. It's not immediately evident, but if you
close and then reopen SpywareBlaster, the status for IE will show one item
has protection disabled. It should work okay if the item is disabled in the
custom block list first, and then the update is applied to the main
application, since the CLSID is only written once to the registry. I
suspect though that even with this approach, the item will be renabled in
the custom block list when the protection is applied in the main
application. I'm not able to test it with the update already applied.

Anyway, to make a long story short, unless you edit the item from the custom
block list, it's probably better to just keep it enabled.

Tom

Tom,
Thanks for the feedback, there is no really comprehensive guidelines currently
for correctly adding / editing the custom block list.
I, too, question the correct manner to perform this task.
As the custom blocking method order to maintain full inoculation would be to
keep all CLSID's blocked, in the main database and in the block list.

I will be posting more information as this is further understood and continues to
evolve.

Silj

--
siljaline

MS - MVP Windows (IE/OE) AH-VSOP
________________________________
Security Tools Updates
http://forum.aumha.org/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)