SpywareBlaster adds a list of domain in IE under Tools -> Internet
Options -> Privacy where you click Edit to see which are listed as
Always Allow and Always Block. SpywareBlaster adds domains with the
Always Block attribute.

Note that Doubleclick has several domains. If you want to deny any
connects Doubleclick, you can define rules in your firewall to block
connections to them. You could try blocking on a URL rule with
".doubleclick." and hope that it only blocks connections to domains with
that in the domain portion of the URL, but it would also block something
like "http://somewhere.com/somepath/my.doubleclick.jpg". So I block on
(and showing some other common polluters):

atdmt.com
doubleclick.com
doubleclick.net
doubleclick.us
doubleclick.org
fastclick.biz
fastclick.com
fastclick.net
hitbox.com
websidestory.com
x10.com

I add these under the Parental Control section in Norton Internet
Security. If you have another firewall and you are using these in a URL
block then prefix them with a period and postfix a trailing slash, like
".doubleclick.com/", just to help ensure you specify a domain and not
some path under it. If your firewall allows you to specify regular
expressions then maybe something like "*.doubleclick.*/" or
"//*.doubleclick.*/" would be usable (you might have to escape the slash
character and have to use "////*.doubleclick.*//").

I actually wanted to use the URL blocking in my router so other hosts on
my intranet wouldn't end up connecting to those sites. Alas my router
doesn't allow many entries in its URL block list nor do they allow
wildcarding. Once the domain or URL blocking is enabled in the
firewall, a good check is to visit http://www.cheaptickets.com/ which
makes extensive use of Doubleclick. The links might still display on
the page (unless you have ad blocking also enabled) but when you click
on them you get a "page not found" or a default page from your firewall
noting the block.

Using a firewall to block connects to Doubleclick will not prevent a web
site from writing cookies that can be used by Doubleclick. My
understanding is that scripts are used to write and read cookies, so if
scripting is disabled then a new cookie cannot be written and an old
cookie cannot be read. But so many legitimate web sites use scripts
that you usually find that you want to leave it enabled. So blocking
the cookie using Always Block in IE is another way to keep clean.
However, using the cookie Always Block only works for the user that is
logged on at the time this list is updated, so other users logging onto
the same host won't be protected unless they also run SpywareBlaster
(and include the cookie immunizations). The cookie allow/block list
gets saved in the registry under
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Internet
Settings\P3P\History"; blocked domains have a value of 5 while allowed
domains gets a value of 1. Since this is a user registry hive, each
user has a different instance of this registry key so each user must run
SpywareBlaster to add the blocked cookie domains.

I use PopUp Cop to eliminate popup windows (rather than disabling
javascript). It has has "dynamic" cookie management. You can use
products like Cookie Wall and others to manage cookies but you end up
periodically having to check and do the deletes yourself, or you end up
having to leave a constantly running background program to monitor
cookies and delete any not on a whitelist. PopUp Cop's cookie
management also uses a whitelist; domains you list will not have their
cookies deleted while all others get purged. It effectively forces all
non-whitelisted cookies to be per-session cookies. Even per-session
cookies sometimes don't get deleted when you exit IE, but PopUp Cop will
make sure they get deleted. Since PopUp Cop is only active when IE is
loaded, and since that's the only time you need cookie management, it
works when it is appropriate rather than leaving some program always
running in the background. You can also choose to ignore cookies from
domains in the Trusted security zone; if the sites are trusted then
presumably you trust their cookies. However, I still leave IE
configured to accept 1st party cookies, BLOCK 3rd party cookies, and
allow per-sesion cookies. A legit domain shouldn't have to use 3rd
party cookies. Another option is to not delete cookies in IE's Always
Allow list. So not only can you specify which domains in PopUp Cop to
keep their cookies but you don't end up obviating IE's own Always Allow
list. Domains can be wildcarded in PopUp Cop's cookie manager so you
can use something like "*.domain.tld" and not have to worry if the
cookie is for the domain or for a subdomain. Rather than disable some
functionality of a site that needs cookies during that session, they can
write and read their cookie but it won't be there after I exit the last
instance of IE.


--
__________________________________________________
Post replies to newsgroup. E-mail not accepted.
__________________________________________________


"Ken Russell" <rusty@theseams.com.au> wrote in message
news:3f84d777$0$14559$afc38c87@news.optusnet.com.a u...
> Spybot will remove existing cookies. To prevent them from
re-infecting, use
> Spyware Blaster http://www.javacoolsoftware.com/spywareblaster.html
>
> Ken Russell
>
> "George Weischadle" <gweischadle@earthlink.net> wrote in message
> news:6l4hb.3710$dn6.1847@newsread4.news.pas.earthl ink.net...
> | I just cleaned and immunized my PC using Spybot. Went online again,
ran a
> | check, and found Doubleclick cookies present. Does immunization
just
> | prevent these cookies from doing their nasty deed, or is it supposed
to
> | prevent them from being written again to the hard drive? Sorry if
this is
> a
> | dumb question - I'm a newbie here ... )
> |
> | George
> |
> |
>
>