Browser Fingerprint [GOOD TIP]

pr0j3ctx

Junior Member
Joined
Feb 24, 2017
Messages
119
Reaction score
68
Thought I'd just drop one of the many things you have to do to custimize your browser when dealing with Facebook account creation or management

WebRTC https://www.innoarchitech.com/what-is-webrtc-and-how-does-it-work/

I would never suggest using Google Chrome for Facebook in terms of testing things or creating and managing accounts. Use a browser you don't use for you day to day activities.

Use Firefox and download this add-on: https://addons.mozilla.org/nl/firefox/addon/happy-bonobo-disable-webrtc/

It's a quick tip, nothing serious!
 
For day to day activities i use firefox but for forums i use chrome lul you leave a finger print anytime you go to a site using the same cookies
 
I use Linux with Firefox, Opera and Chromium (not chrome). Already dump Chrome years ago. You can disable WebRTC, javascript and cookies by searching within Opera and Chromium settings, and for Firefox, you can use about:config command to disable that.
 
Last edited:
You are avoiding WebRTC , but what about font fingerprints , etc. ?

Really false sense of security :)

Code:
List of fingerprinting sources:
UserAgent
Language
Color Depth
Screen Resolution
Timezone
Has session storage or not
Has local storage or not
Has indexed DB
Has IE specific 'AddBehavior'
Has open DB
CPU class
Platform
DoNotTrack or not
Full list of installed fonts (maintaining their order, which increases the entropy), implemented with Flash.
A list of installed fonts, detected with JS/CSS (side-channel technique) - can detect up to 500 installed fonts without flash
Canvas fingerprinting
WebGL fingerprinting
Plugins (IE included)
Is AdBlock installed or not
Has the user tampered with its languages 1
Has the user tampered with its screen resolution 1
Has the user tampered with its OS 1
Has the user tampered with its browser 1
Touch screen detection and capabilities
Pixel Ratio
System's total number of logical processors available to the user agent.
Device memory
 
You are avoiding WebRTC , but what about font fingerprints , etc. ?

Really false sense of security :)

Code:
List of fingerprinting sources:
UserAgent
Language
Color Depth
Screen Resolution
Timezone
Has session storage or not
Has local storage or not
Has indexed DB
Has IE specific 'AddBehavior'
Has open DB
CPU class
Platform
DoNotTrack or not
Full list of installed fonts (maintaining their order, which increases the entropy), implemented with Flash.
A list of installed fonts, detected with JS/CSS (side-channel technique) - can detect up to 500 installed fonts without flash
Canvas fingerprinting
WebGL fingerprinting
Plugins (IE included)
Is AdBlock installed or not
Has the user tampered with its languages 1
Has the user tampered with its screen resolution 1
Has the user tampered with its OS 1
Has the user tampered with its browser 1
Touch screen detection and capabilities
Pixel Ratio
System's total number of logical processors available to the user agent.
Device memory
This.

To OP: This is really old story. If you figured this out only now, it's pretty late to say the least. The first mention of it on BHW was in 2014 and the first thread which dealt with it was posted 3 years ago: https://www.blackhatworld.com/seo/webrtc-may-be-leaking-your-ip-windows-chrome-firefox.740017/.

Not just FF, but Chrome and Opera too can be protected against WebRTC leakage and canvas fingerprinting, there are multiple addons for both: WebRTC Leak Prevent and Canvas Defender is what i'm using on Chrome. If you fancy Opera and an addon is not natively available, which is available for Chrome, you can install it using this addon: https://addons.opera.com/en/extensions/details/download-chrome-extension-9/.
Or instead of stuffing your browser with every kind of addons, you can use something like Multiloginapp, which can be used with 10 browser profiles for free.
 
You are avoiding WebRTC , but what about font fingerprints , etc. ?

Really false sense of security :)

Code:
List of fingerprinting sources:
UserAgent
Language
Color Depth
Screen Resolution
Timezone
Has session storage or not
Has local storage or not
Has indexed DB
Has IE specific 'AddBehavior'
Has open DB
CPU class
Platform
DoNotTrack or not
Full list of installed fonts (maintaining their order, which increases the entropy), implemented with Flash.
A list of installed fonts, detected with JS/CSS (side-channel technique) - can detect up to 500 installed fonts without flash
Canvas fingerprinting
WebGL fingerprinting
Plugins (IE included)
Is AdBlock installed or not
Has the user tampered with its languages 1
Has the user tampered with its screen resolution 1
Has the user tampered with its OS 1
Has the user tampered with its browser 1
Touch screen detection and capabilities
Pixel Ratio
System's total number of logical processors available to the user agent.
Device memory

Of course, I thought I mentioned that this was only a tip? I'm not dropping the full system that I use on a forum
Either way, most of the fingerprinting in that list is not determining or useful either way

If someone thinks that WebRTC is enough then please think again. I've got lots of experience in this field by the way so I know which fingerprints matter
 
I suggest to check multiloginapp and their blog, there is everythink about fingerprints
 
I suggest to install fresh system on vmware (can be linux, it's faster). Then you have "fresh" fingerprint, easy and fast way ;)
 
I use Brave browser and can honestly say I've never had a problem since using it.
 
Thanks for the share. But be careful because if there's close to no data for Facebook to see, that also becomes suspicious.
E.g. cookies: how many people have a browser with 0 cookies? Right
It's true, they need some data from you else it flags in their system - same with profiles with no pictures etc
 
Thanks for the share. But be careful because if there's close to no data for Facebook to see, that also becomes suspicious.
E.g. cookies: how many people have a browser with 0 cookies? Right
would you tell me how I can ignore that ? thanks
 
Back
Top