Unstable 'canvas' entropy source when runs in a cross-origin iframe about fingerprintjs HOT 10 CLOSED

@tvvocold Thank you for the detailed issued report, especially the code and the logs diff. But unfortunately I can't reproduce it. Could you please provide more details:

1. Does it always happen on your device?
2. Do the top page and the iframe use different origins? Are they HTTP, HTTPS or localhost?

Anyway, canvas is known to be unstable, and there is nothing we can really do about it. If you want more stability, you can exclude one or both canvas images, which will also reduce the selectivity. Interestingly, the geometry canvas is more stable, but you've got it different.

from fingerprintjs.

@Finesse

1. Does it always happen on your device?

Yes, always, even I had restart the Safari and clear the cache.

2. Do the top page and the iframe use different origins? Are they HTTP, HTTPS or localhost?

They are both served with HTTPS, SSL signed by Valet

from fingerprintjs.

Are the top page and the iframe served from the same origin?

from fingerprintjs.

Does the problem occur when you follow these steps?

from fingerprintjs.

Are the top page and the iframe served from the same origin?

Nope. Different origin: finger1.test and finger2.test

from fingerprintjs.

Weird, it's OK now, might be the cache issue, thx, and I will let you know(and reopen this issue) if there are diff again.

from fingerprintjs.

@Finesse Just saw this bug again, but I don't know how to reproduce it
The log is here: https://www.diffchecker.com/Rfs3Ll6W
and the code is the same as before: https://gist.github.com/tvvocold/97c968d35247e5184959367baf17fc98
btw the strangest thing is that every time I refresh the page, sometimes it returns to normal, and sometimes it starts to be unstable again.

from fingerprintjs.

Does the problem occur when you follow these steps?

from fingerprintjs.

Does the problem occur when you follow these steps?

Nope. Still can't reproduce this bug stably

from fingerprintjs.

Thanks for trying. Anyway, I'm closing this issue as a duplicate of #768. There is nothing we can do with it now, sorry.

from fingerprintjs.