IP Cookies: For lack of a better name

[hpguru]

I mentioned in an earlier post that Webcrawler is inserting visitors IP addresses into their search queries. My Personal Info Protector filter blocked this but today I got to thinking it might be better to replace my IP with say 127.0.0.1 or 0.0.0.0 since I like using Webcrawler from time to time.

So I wrote a couple filters, one for the url replacement and another for the associated referer. Didn't really know what to call them so I thought that this is somewhat like a cookie that is stored on the server, hence IP Cookies.

[HTTP headers]
In = FALSE
Out = TRUE
Key = "Referer: IP Cookies I (out)"
Match = "XXX.XXX.XXX.XXX1"
Replace = "127.0.0.11"


In = FALSE
Out = TRUE
Key = "URL: IP Cookies II (out)"
Match = "XXX.XXX.XXX.XXX1"
Replace = "$JUMP(127.0.0.11)"

To use the filters replace the string XXX.XXX.XXX.XXX with your IP address. If you are on a dialup or you have a dynamic IP address that changes frequently then you may as well not bother with these filters.

Any thoughts?


Facing each other,
a thousand miles apart.

[hpguru]

Here is another filter just for Webcrawler which you don't have to change. It will work regardless of your IP.

Name = "Webcrawler IP Cookies"
Active = TRUE
Multi = TRUE
URL = "*.webcrawler.com/"
Bounds = "<input*name=$AV(userip)*>"
Limit = 55
Match = "value=$AV(*)1"
Replace = "value="127.0.0.1"1"

Facing each other,
a thousand miles apart.

[Jor]

Good filters. I was unaware Webcrawler had resorted to this kind of IP tagging... the filters are part of my config set now

 

[hpguru]

Hi Jor, Glad you like them. Can you think of a better name for them?

Facing each other,
a thousand miles apart.

Edited by - hpguru on 31 Aug 2002  02:48:21

[Jor]

IP Cookie is a good name, imnsho...

I certainly can't think of another name suitable to this privacy intrusion...

 

[hpguru]

I created a simple filter to alert me when my IP address is matched and found another site that is doing this. Dogpile.com and possibly Findwhat.com. Here's a filter for Dogpile.

Name = "DogPile: Kill FindWhat.com IP Cookies"
Active = TRUE
URL = "search.dogpile.com"
Bounds = "<a*href=$AV(*findwhat.com/results.asp*ip_address=*)*>"
Limit = 800
Match = "*href=$AV(*ip_address=*;mt=)*"
Replace = "<a href="http://findwhat.com/results.asp?MT=&filter_pref=0" "
          "target="_blank">"

Now you know why they call it "Dogpile". BTW the replacement url I chose should allow you to bypass acceptance of their results preference cookie and assumes you would want unfiltered results. I haven't tested this filter except in the test window but it should work.

Facing each other,
a thousand miles apart.

[JD5000]

How 'bout this one?

In = FALSE
Out = TRUE
Key = "IP-Blocker: Protect IP"
Match = "$URL(=44.44.44.443)"
Replace = "IP blocked - u $JUMP(=$LST(ClientIP)13)"

You'll need Jak's ClientIP list.
http://asp.flaaten.dk/pforum/topic.asp?ARCHIVE=&whichpage=3&TOPIC_ID=539

--------
Infopros Joint :: Computer Related Links And Discussion

Edited by - JD5000 on 31 Aug 2002  07:41:04

[hpguru]

Hmmmmmmmmmmmm...

Facing each other,
a thousand miles apart.

[hpguru]

JD, I just tried your filter and it's working good but I would recommend omitting the equal sign. If it is missing or some other character precedes your IP then the filter won't match and you are tagged & bagged.


Edit: I would also delete the u or replace it with h since it sends that header with your IP included.

Edited by - hpguru on 31 Aug 2002  19:21:19

[hpguru]

Here's my take

 

In = FALSE
Out = TRUE
Key = "IP-Cookie: IP Cookie Spoofer (Out)"
Match = "$URL(XXX.XXX.XXX.XXX3)"
Replace = "IP Cookie Spoofed!$JUMP($LST(ClientIP)13)"

 

Facing each other,
a thousand miles apart.

[hpguru]

Here is another to take care of IP Cookies in 302 redirects. It will prevent your browser from being redirected twice.

In = TRUE
Out = FALSE
Key = "Location: IP Cookie Spoofer (In)"
Match = "XXX.XXX.XXX.XXX3"
Replace = "$LST(ClientIP)13"

Facing each other,
a thousand miles apart.

[TEggHead]

quote:
Here is another to take care of IP Cookies in 302 redirects. It will prevent your browser from being redirected twice.

forgive me for sounding dense, but if your IP is present on incoming 302 redirect, that means your IP has already left the building...yer too late...



Edited by - TEggHead on 31 Aug 2002  20:41:06

[hpguru]

Well of course. If they didn't already have your IP there would be no connection at all. These filters simply address how your IP is being used in meta data appended to the url, not to prevent them from getting your IP address. After all, they aren't appending your IP and other meta data to your query just to make it profound looking.

Facing each other,
a thousand miles apart.

Edited by - hpguru on 31 Aug 2002  21:07:28