pt
>>>>> creation of properties with a given name (e.g. "mainkey") would be to run
>>>>> with `--nouse-ic` and put a breakpoint on StoreIC::Store(). This is
>>>>> (obviously?) not an officially supported feature, and I haven't tried it,
>>&
of Chrome. Be sure to set v8_optimized_debug =
>>> false in args.gn beforehand.
>>> - run with each renderer in a debugger: out/debug/chrome --no-sandbox
>>> --disable-hang-monitor --disable-extensions --js-flags="--nouse-ic"
>>> --renderer-cmd-prefix=
xterm -e gdb -args"
> - bring a large amount of patience to both of these steps, and have enough
> RAM in your machine (64GB is good, dunno if 32GB is enough)
>
> Good luck!
>
>
> On Wed, Nov 9, 2022 at 3:19 PM Filip Petronijevic
> wrote:
>
>> Ok, I'll explai
Ok, I'll explain what problem I have and if there is any way of solving it.
Imagine I have following Javascript code:
var obj1= {}
obj1["mainkey"] = {canvasComputed: "oewrewqioewrerqewjoijiqerw", todata:
"somerandomdata"}
var obj2= {}
obj2["mainkey"] = "some big string"
var obj3 = {}
First of all, thank you for responding back!
I'm well aware of very broad commercial and non commercial fingerprintable
methods including those that you have posted, but nothing like that is what
they are doing. As previously said, they seem to be doing something very
weird as even swapping
Hello, during my academic research I came across one website which has very
disturbing levels of fingerprinting. It manages to detect that I come from
same device despite me hooking, randomizing and changing more then 850 >0.0
entropy values. Including using VPN connection or proxies. I found
