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

Support adding custom fingerprint database files when use tech-detect flag #1803

Open
nbxiglk0 opened this issue Jul 5, 2024 · 1 comment
Assignees
Labels
Type: Discussion Some ideas need to be planned and disucssed to come to a strategy. Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@nbxiglk0
Copy link

nbxiglk0 commented Jul 5, 2024

Hi,Team

When using the fingerprint recognition feature, the fingerprint database comes from the built-in https://github.com/projectdiscovery/wappalyzergo, sometimes I need to add some of my own app fingerprints to be recognized when scanning.

Please describe your feature request:

Accepts a user-specified fingerprint data file. The file format is consistent with https://github.com/projectdiscovery/wappalyzergo/blob/main/fingerprints_data.json. When the user specifies a custom fingerprint data file, the fingerprint recognition rule will use the user-specified file instead of the built-in default rule.
This file can be specified in config.yaml or on the command line.like httpx -l urls.txt -tech-detect -custom-finger finger.json

@nbxiglk0 nbxiglk0 added the Type: Enhancement Most issues will probably ask for additions or changes. label Jul 5, 2024
@dogancanbakir dogancanbakir self-assigned this Jul 5, 2024
@dogancanbakir dogancanbakir added the Type: Discussion Some ideas need to be planned and disucssed to come to a strategy. label Jul 5, 2024
@GeorginaReeder
Copy link

Thanks so much for your feature request @nbxiglk0 - we'll take a look into this! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Discussion Some ideas need to be planned and disucssed to come to a strategy. Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

No branches or pull requests

3 participants