Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce tests of fingerprint cosinstency #26

Open
petrpatek opened this issue Jan 10, 2022 · 3 comments
Open

Introduce tests of fingerprint cosinstency #26

petrpatek opened this issue Jan 10, 2022 · 3 comments
Assignees
Labels
antibot Yet another antibot service is recognizing the injection t-tooling Issues with this label are in the ownership of the tooling team.

Comments

@petrpatek
Copy link
Contributor

petrpatek commented Jan 10, 2022

As Gavin mentioned we could use https://github.com/abrahamjuliot/creepjs for fingerprint consistency testing.

@JaneJeon
Copy link

+1 for this. fingerprint-injector + using actual Chrome is literally enough to avoid detection from basically all websites that I've tested on, except for CreepJS.

It's actually kinda crazy, but there are only a few points that are detected by creepJS (mainly the navigator) - so I believe testing with this to try to advance the "arms race" would be absolutely necessary for this project's longevity.

@petrpatek
Copy link
Contributor Author

Exactly, I am glad that it works for you! From my perspective, I want to start testing to validate if the improvements we are doing are improvements at all.

@JaneJeon
Copy link

JaneJeon commented Feb 19, 2022

Well, for what it's worth, CreepJS apparently detected "lies" in the navigator (both the main thread and the service worker) that the injector either didn't cover or they used some magic to detect tampering with it (still trying to figure out which is the case).

Obviously YMMV as I was relying on local Chrome, but I'm trying to make this more.... "scientific" by spinning up puppeteer/chrome in docker and running the test w/ creepjs to get a replicable result.

And I guess the end goal is to test this against actual websites with strong scraping protection, but at the moment, it's just me running it locally against a particular URL/website and seeing what sticks and what doesn't

@barjin barjin transferred this issue from apify/fingerprint-injector Jul 5, 2022
@barjin barjin added the antibot Yet another antibot service is recognizing the injection label Jul 8, 2022
@barjin barjin self-assigned this Jul 21, 2023
@barjin barjin added the t-tooling Issues with this label are in the ownership of the tooling team. label Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
antibot Yet another antibot service is recognizing the injection t-tooling Issues with this label are in the ownership of the tooling team.
Projects
None yet
Development

No branches or pull requests

3 participants