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

Add plugin injection support #32

Open
petrpatek opened this issue Oct 25, 2021 · 2 comments
Open

Add plugin injection support #32

petrpatek opened this issue Oct 25, 2021 · 2 comments
Assignees
Labels
t-tooling Issues with this label are in the ownership of the tooling team.

Comments

@petrpatek
Copy link
Contributor

We should also inject the collected plugin data for supported browsers.

@barjin barjin transferred this issue from apify/fingerprint-injector Jul 5, 2022
@barjin
Copy link
Collaborator

barjin commented Jul 7, 2022

I see that the plugins data (along with mime-types) are being already generated in the fingerprint-generator. Injecting those will probably not be any different from all the other properties. Is this somehow connected to #27 ? Thanks!

@petrpatek
Copy link
Contributor Author

Yes, there is some weirdness with linking the plugins and mime-types together. I did a PR in the old repo. I am also afraid that injecting some no standard plugin could introduce way more uniqueness and actually the fingerprint could be easier to track and also won't blend with the site traffic. This is one of the reasons why we need to have tests for the performance of the fingerprint on the most popular protections.

@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
t-tooling Issues with this label are in the ownership of the tooling team.
Projects
None yet
Development

No branches or pull requests

2 participants