https://browserprint.info/
https://panopticlick.eff.org/
http://ip-check.info
http://browserleaks.com/
http://browserspy.dk/
Fingerprinting is the newest way of tracking you across websites.
It's being done right now by companies like Google.
Because unlike cookie based tracking you can't defeat it just by disabling cookies.
There is currently NO FOOLPROOF DEFENCE against fingerprinting (except quitting the Internet).
Google's privacy policy states
>Other technologies are used for similar purposes as a cookie on other platforms where cookies are not available or applicable
https://www.google.com/intl/en/policies/privacy/key-terms/#toc-terms-cookie
ReCAPTCHA probably still contains fingerprinting code:
https://archive.is/9K5gs
This means that the majority of 4chan users could be being fingerprinted, and Google might know about your shitposting habits even if cookies are disabled.
Google releases limited hangout of how much they know about you:
https://news.slashdot.org/story/16/06/29/2038257/googles-my-activity-reveals-how-much-it-knows-about-you
Daily reminder to do all your Amazon / eBay / LinkedIn / botnet shit in a completely separate browser to your Googling or buying shit.
It's currently the ONLY way to truly defend against fingerprint tracking.
Double points if you have each browser running in a different VM with a different OS.
Triple points if you have each browser's VM configured with a different VPN connection.
Could the FP-Block browser extension be exactly what we're looking for?
http://satoss.uni.lu/software/fp-block/
Adds randomness to canvases, generates random and consistent HTTP headers, randomises timezone, etc.
Bit buggy, and it doesn't seem to play well with other extensions, but very promising.
If only it was under active development.
Other uncommon extensions you may want to check out
https://addons.mozilla.org/en-US/firefox/addon/canvasblocker
https://addons.mozilla.org/en-US/firefox/addon/blender-1
>>55600552
Yeah it's got a nice feature set, but just rotating fingerprints each n seconds doesn't really cut it.
It's important that you don't use the same fingerprint in sites with login and other sites.
In the Panopticlick study 83.6% of fingerprints were unique, even when JavaScript and/or Flash was disabled.
That's crazy.
Canvas fingerprinting is the big boogeyman, but it's not even needed when simply looking at HTTP headers can work so well.
>>55610820
And when JavaScript and/or Flash was enabled fingerprints were unique 94.2% of the time.
This is before canvas fingerprinting was even invented.
The stuff that Google is openly collecting via is probably plenty to identify you.
>>55609113
>Double points if you have each browser running in a different VM with a different OS.
How about just using Tails in the VMs?
>>55611443
Well if you use the same OS in each VM it kinda defeats the purpose.
Tor has some good fingerprinting defenses but it's not perfect yet.
Someone should do a study of how unique Tor users and Tails users are.
Personally I don't use Tor for regular browsing because of its speed, even a single proxy can be annoyingly slow, and Tor uses 3
>>55609113
For reading the screen resolution with CSS, would that work inside of a frame or would they just get the size of the frame? If it's the later, would that still be an applicable way to fingerprint people using the noscript captcha?
>>55611531
It gets the screen size.
Tested in IceCat.
You can test too by putting this in a html file:
<html>
<body>
<iframe src="https://browserprint.info/captcha"/>
</body>
</html>
Blender doesn't make sense. It says it sets
>the operating system to be Windows 8.1 64-bit
This makes sense since it's a common operating system
>Firefox to be version 36
Why use an old version instead of the latest? Since 99% of all people will leave auto-update on they're going to be on the latest version. From what I can find, version 36 of Firefox isn't even used by 0.10%.
>the language to be English
Global language so it's okay.
>the accepted charsets to be unspecified
Pretty sure all major web browsers specify a value for this so leaving it empty will stand out.
>>55611504
Tor isn't optimized for speed, it's focused on concealing your real identity. If you don't enable JavaScript, don't run plugins and don't resize the window there's very little information to be gathered except for HTTP headers, which unless you modify it, will be the same for all Tor users.
>>55611531
You could create a local HTML document with a frame containing https://browserprint.info and see what it reports.
>>55611595
Okay... Just noticed Blender hasn't been updated for over a year so that explains why Firefox version is 36.
>>55611504
>Well if you use the same OS in each VM it kinda defeats the purpose.
It should still prevents some tracking between websites as there is no shared storage between the VMs. The advantage to Tails is that it's a standardized live CD as opposed to a everyone's different VMs. If everyone settles on one standardized distro then most all of what will get returned even with scripts on will be the same across a large group of people and the data will be worthless.
>>55611595
Someone should modify blender to use the same headers as TBB.
>>55611632
Ideally everyone should settle on standardized screen sizes for the VMs too, but that might be harder to get people to agree on.
>>55611641
I'm 99% done doing this, but then I realized that blender doesn't work at spoofing the language.
Not sure if I should bother
>>55612538
Decided not to release something broken.
Left a review saying the extension was broken, maybe the author will update
