polkadot
Carder
- Messages
- 61
- Reaction score
- 32
- Points
- 18
I have tried different “antik”
Gologin, linkensphere, kameleo I have configured them in different ways but they all have the same bug, the hash or fingerprint that corresponds to Audio is always the same, it does not change even if I choose the noise option.
My questions are:
1.Will having the audio hash the same in any profile that is created cause the anti-fraud to determine that it is the same device or will it increase the fraud rate?{
2. Changing all the fingerprint, Canva, webgl, audio, properties, fonts, but keeping the same audio generates a different fingerprint or on the contrary the anti-fraud system saves the hash in a database that then compares with other fingerprints and if it finds similarity it detects the inconsistency in the fingerprint?
Finally, my conclusion, if I'm wrong, please correct me to clarify my doubts.
I understand that for the "antik" to be configured correctly, the canvas, webgl, audio, font, rects, properties must be different in each profile, obviously the hardware too, but in this section I'm asking only about the hashes that each fingerprint generates, I understand that each hash is unique for each browser and that the probability of there being two identical hashes produced by different devices is almost negligible, with this clear my reflection is that for the environment in the "antik" to be configured correctly, the software used must generate profiles with the mentioned hashes always different, so far I have not found any that is capable of doing it consistently, what I mean by consistent is that when generating a different hash for each profile it is not detected by the pixelscan or fv.pro filters as false.
If on the contrary, if the hashes of the canva webgl font rect and the hardware are different, it is enough for the unique fingerprint that identifies the device to change, please clarify it for me and if not, what do I think, that "antik" is capable of generating profiles with all the mentioned hashes different that pass the fv.pro and pixelscan filters.
Thanks for reading and for your help
Gologin, linkensphere, kameleo I have configured them in different ways but they all have the same bug, the hash or fingerprint that corresponds to Audio is always the same, it does not change even if I choose the noise option.
My questions are:
1.Will having the audio hash the same in any profile that is created cause the anti-fraud to determine that it is the same device or will it increase the fraud rate?{
2. Changing all the fingerprint, Canva, webgl, audio, properties, fonts, but keeping the same audio generates a different fingerprint or on the contrary the anti-fraud system saves the hash in a database that then compares with other fingerprints and if it finds similarity it detects the inconsistency in the fingerprint?
Finally, my conclusion, if I'm wrong, please correct me to clarify my doubts.
I understand that for the "antik" to be configured correctly, the canvas, webgl, audio, font, rects, properties must be different in each profile, obviously the hardware too, but in this section I'm asking only about the hashes that each fingerprint generates, I understand that each hash is unique for each browser and that the probability of there being two identical hashes produced by different devices is almost negligible, with this clear my reflection is that for the environment in the "antik" to be configured correctly, the software used must generate profiles with the mentioned hashes always different, so far I have not found any that is capable of doing it consistently, what I mean by consistent is that when generating a different hash for each profile it is not detected by the pixelscan or fv.pro filters as false.
If on the contrary, if the hashes of the canva webgl font rect and the hardware are different, it is enough for the unique fingerprint that identifies the device to change, please clarify it for me and if not, what do I think, that "antik" is capable of generating profiles with all the mentioned hashes different that pass the fv.pro and pixelscan filters.
Thanks for reading and for your help
