Послать post запрос через http клиент с твоими куками из браузера и с headers которые тебе решалка дала, потом после запроса смотришь на какую страницу был переход, берешь куки с хттп клиента и переходишь на следующий url.
[CanvasInspector3] Multiple different PerfectCavans request items
-
Hello
I'm using CanvasInspector3 with FingerprintSwitcher (Obtain fingerprint from server) to scan a site and obtain Request code to use with PerfectCanvasFingerprint in Bablosoft. In CanvasInspector3 I click on "Save request" and repeat the process. Sometimes, additional Canvas Fingerprint activities appear (usually 2, sometimes 4 or 5).
My question:
When saving a request in CanvasInspector3, why does it say "It is recommended to use only those PerfectCanvas request items which are present after both starts."?
For the most accurate spoofing, wouldn't it make sense to repeat the process many times and save the request for all fingerprint activities? Isn't this the best way to make sure all Canvas Fingerprint activities look genuine/legitimate? Or is it just saying that because generating PerfectCanvasFingerprint with many fingerprint activities in the Request Code takes longer? Maybe I just misunderstand the system, but I'd appreciate if someone could clear things up for me. Because for me personally, the time to obtain PerfectCanvas Fingerprints is irrelevant. I just want to make sure everything is spoofed as good as possible. Thanks -
Вопрос: В CanvasInspector3 говорится, что нужно сохранять только "Canvas холста", которая появляется при нескольких попытках. Почему? Не разумнее ли сохранять всю активность, даже если она появляется только иногда? Цель состоит в том, чтобы иметь наилучшую и наиболее подлинную подделку.
-
@simplyx said in [CanvasInspector3] Multiple different PerfectCavans request items:
Вопрос: В CanvasInspector3 говорится, что нужно сохранять только "Canvas холста", которая появляется при нескольких попытках. Почему? Не разумнее ли сохранять всю активность, даже если она появляется только иногда? Цель состоит в том, чтобы иметь наилучшую и наиболее подлинную подделку.
As far as I remember, this explanation is in the description of the action: If the value of PerfectCanvas is always different, then the site will not be able to collect the canvas database from real devices and identify it by this attribute.
-
@Fox
Thanks for the reply. The value of PerfectCanvas isn't always different. The difference lies within how many Canvas Elements (Activities) are rendered / requested, despite doing the exact same actions on the exact same site. To clarify, here an example:CanvasInspector 3
Use profile: No
Use proxy: Yes (rotating all 5 minutes)
Use Fingerprint: Yes (obtain from server)Start Browser --> Open Website "Example.site" --> Click "Next" and "Agree" --> Save Canvas Request
Repeat 10x - Exact same site, exact same "Next" and "Agree" button.
Result:
A(8/10): 3 fingerprint activities (toDataURL): "CC" "DD" "EE" - Request Code = "X" - always the same
B(2/10): 5 fingerprint activities (toDataURL): "CC "DD" "EE" "FF" "GG" - Request Code = "Y" - always the sameIn this case, can I just use the Request Code from "B"? The fingerprint activities from "A" are included in "B". Or should I only use the Request Code From "A", as these fingerprint activities appear 100% of the time? I don't know why sometimes it's 3 fingerprint activities and sometimes 5. It seems to be random and not connected to proxy IP quality or fingerprint.
¨ -
Problem still persists. Not always is the same combination of Canvas Elements loaded. Because the combination seems to be random, I can't predict which Request Code I should use for the Perfect Canvas Fingerprint generation. I don't understand why it isn't possible to always cover all Canvas Elements, even if only a few of them are loaded. All of them are know, just the combo changes.
