Skip to content
This repository has been archived by the owner on Feb 25, 2020. It is now read-only.

chameleon not working #21

Open
ucnavryp opened this issue May 17, 2015 · 13 comments
Open

chameleon not working #21

ucnavryp opened this issue May 17, 2015 · 13 comments

Comments

@ucnavryp
Copy link

Hello,
chameleon(latest verison and old verisons) not working anymore, it is NOT BLOCKING ANYTHING

test:
www.whoer.net
www.ip-check.info

I am tested Google Chrome 42, Srware Iron 42, Google Chrome 28

PLEASE FIX

@ghostwords
Copy link
Owner

Chameleon in the master branch no longer attempts to masquerade as Tor Browser, in preparation for #1. Note that Chameleon never did anything to hide your real IP address.

I'll keep this issue open until I update the README with current status.

@ucnavryp
Copy link
Author

thanks for the reply, I know this but Chameleon not working

it is not blocking,ex: timezone, useragent, screen etc.etc..

screenshot:
http://s16.postimg.org/fs6w5oqd0/Untitled.jpg

@ghostwords
Copy link
Owner

That's what I meant when I wrote Chameleon no longer attempts to masquerade as Tor Browser.

In the future, Chameleon will do a combination of subtle randomization of properties (don't try to make Chrome look like Firefox, make more inconspicuous tweaks instead) and blocking known fingerprinters outright.

The README is out-of-date at this point, but the WARNING part very much applies still.

@ucnavryp
Copy link
Author

randomization not working :/
http://s22.postimg.org/mu3cun874/Untitled.jpg

@ghostwords
Copy link
Owner

Right, it's not implemented yet.

@0xBRM
Copy link

0xBRM commented May 17, 2015

Well, then, unless you randomise those properties on a web request basis, youll be very unique for n minutes.

@ghostwords
Copy link
Owner

If you generate fifteen different fingerprints over fifteen browsing instances, you should be more private, right? You are making it harder for persistent tracking to occur. Tracking within a browsing instance (maybe a browser session, maybe a page load) seems less problematic than tracking over longer periods of time, across multiple devices (cross-device tracking protection needs more research).

@0xBRM
Copy link

0xBRM commented May 17, 2015

If you're unique, you will still be trackable over a single browsing instance/session, which can still reveal quite a lot of information about your browsing habits. Hence what I said about generating fingerprints on a per tab basis, but common ones nonetheless.
You can blend in, and randomise it simultaneously.

@stteven
Copy link

stteven commented Sep 3, 2015

Hi, no news after several months, chameleon still doesn't work on last chrome version. Any eta about fix? Thanks

@ghostwords
Copy link
Owner

No ETA, sorry. There is much to do here yet, and I am interested in continuing; it's a matter of finding the time. Thanks for your interest!

@chrcoluk
Copy link

no new release at all in 2016, dead project sadly.

@ghostwords
Copy link
Owner

Hi @chrcoluk, please see #26.

@Atavic
Copy link

Atavic commented Feb 24, 2017

If official google chrome is used, the User Agent simply cannot be hidden from fingerprinting.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants