Quote:
Originally Posted by Davy
Interesting.
Where would you store all that info? In a database?
|
In it's simplest form, you would take all those paramters of the fingerprint and make an hash of it (eg MD5: 32-digit character string) and store that. On subsequent visits, compare the hash value of the user against the hashes in the db.
This however kills all possibility of detecting the same user coming back after eg they installed/remnoved 1 font, or ones that updated their browser, since the algorithm to extrapolate/interpolate (not sure which is the best to define) the difference between fingerprints to link one fingerprint to another due to slight changes would lose all information by hashing it. I think for the most part the hash structure is the least database and CPU intensive with the caveat it will give more false negatives due to users updating browser/font/anything.