-
Notifications
You must be signed in to change notification settings - Fork 307
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
Adding a module #312
Comments
Hi, I am grateful for any help. |
They're useful if you want to load ZGrab output directly into a database such as Elasticsearch or BigQuery. However, they're likely out-of-date / wrong, and not particularly well tested, so we should probably move them to an examples directory or similar. If you're adding a module, I wouldn't worry about them. |
Thanks for the quick reply.So if I want to change the JSON output of an existing module, I have to adapt the go files in the corresponding module folder?On Aug 2, 2021 20:05, David Adrian ***@***.***> wrote:
They're useful if you want to load ZGrab output directly into a database such as Elasticsearch or BigQuery. However, they're likely out-of-date / wrong, and not particularly well tested, so we should probably move them to an examples directory or similar. If you're adding a module, I wouldn't worry about them.
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.
|
Yes |
Hi,
If I understand correctly, each application protocol has its own module. Can anyone just give me a brief overview of how to add a new module for a protocol. How does a module work exactly and where does
zgrab2_schemas
come into play here?What would be the procedure I'd have to go through to add a module for a protocol all in all?
Thank you in advance.
The text was updated successfully, but these errors were encountered: