Page 1 of 1

NoScript & Tracking Cookies

Posted: Sat Aug 22, 2009 6:26 pm
by phule
Can NoScript block tracking cookies and if so, how? They seem to be issued by sites with different domain names than the names of the cookies.

Using the application MacScan for the last five weeks, I've identified 8. But the most persistent offenders are as follows:

rotator.adjuggler.com
www.burstnet.com
data.coremetrics.com

I know that adjuggler.com is in my blacklist but it doesn't seem to be blocking rotator.adjuggler.com

Any idea or suggestions are welcomed. TIA

PS. Following is the complete list of tracking cookies:

ads.adap.tv
ads.realtechnetwork.net
data.coremetrics.com
metrics.mms.mavenapps.net
rotator.adjuggler.com
server.iad.liverperson.net
www.burstnet.com
www.googleadservices.com

Re: NoScript & Tracking Cookies

Posted: Sat Aug 22, 2009 9:31 pm
by Foam Head
NoScript isn't meant to manage HTTP Cookies and thus it doesn't stop the generic tracking cookies you mentioned. However, since it can be a security risk to allow HTTP access to HTTPS cookies, NoScript has an option to help prevent this kind of cookie hijacking (see FAQ Questions 6.4).

If you are concerned about tracking cookies, you can uncheck FireFox's Options | Privacy | Accept third-party cookies (which helps, but won't eliminate them), use an after the fact cleaner (like Ad-Aware), or use a FireFox cookie manager add-on.

-Foam

Re: NoScript & Tracking Cookies

Posted: Sun Aug 23, 2009 4:46 pm
by phule
Foam Head wrote:NoScript isn't meant to manage HTTP Cookies and thus it doesn't stop the generic tracking cookies you mentioned. However, since it can be a security risk to allow HTTP access to HTTPS cookies, NoScript has an option to help prevent this kind of cookie hijacking (see FAQ Questions 6.4).

If you are concerned about tracking cookies, you can uncheck FireFox's Options | Privacy | Accept third-party cookies (which helps, but won't eliminate them), use an after the fact cleaner (like Ad-Aware), or use a FireFox cookie manager add-on.

-Foam
Nuts! But thanks for the reply anyway.