-
Notifications
You must be signed in to change notification settings - Fork 153
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 <detection></detection> on report import #1405
Conversation
When importing a report with <detection> and even if it has the correct nvt as a host_detail as well as an result within the report the detection block was missing when importing via create_report. To add those sections two new entries within host_details will be added when a <detection> got found within a result.
Co-authored-by: Jaspar L. <[email protected]>
if else if formatting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing I'm missing are the detected_by@...
details I've noted below.
Other than that and a few things about code formatting, the PR already looks good to me.
Co-authored-by: Timo Pollmeier <[email protected]>
To have more fine grnaular control over the found detections the location should be included into detected_by.
This reverts commit 9ee207e.
you're right changed it to use |
What:
When importing a report with and even if it has the correct
nvt as a host_detail as well as an result within the report the
detection block was missing when importing via create_report.
To add those sections two new entries within host_details will be added
when a got found within a result.
Why:
How did you test it:
To test it you need to have a report with
in it, the source_oid of those detection must be also available as result nvt oid entry.
With that given you need to import that report into an container task and then download the report via gsa.
Checklist: