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

Move members from custom element to vt element inside the vts dictionary #33

Merged
merged 8 commits into from
Nov 21, 2018

Conversation

jjnicola
Copy link
Member

Several tags which were before in custom element, are now an explicit member of each vt.

Depends on PR greenbone/ospd#73

the custom element.
It will be used in case of no qod_type.
It returns the detection element at least with qod or qod_type, since
it is possible that there is no vuldetect tag for a script.
The qod/qod_type tag was moved in vts dictionary. It is not under custom
member anymore.
Members of the dict are cvss_base_vector, cvss_base from the script tags,
and also cvss_type and cvss_origin.

Add get_severities_vt_as_xml_str(), which returns a severity xml element in
string format.

Remove unused get_nvt_severity() method.

Fix severities in results.
Necessary to improve debugging. Before was not possible to know the
problematic vt.
Improve logging for get_refs_vt_as_xml_str and get_severities_vt_as_xml_str
Copy link
Member

@janowagner janowagner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested this successfully.
Some Errors occurred when dumping all vt's, but this appears due
to inconsistency in the NVTs.

@jjnicola jjnicola merged commit 5a1a620 into greenbone:master Nov 21, 2018
@jjnicola jjnicola deleted the vt-elements branch November 21, 2018 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants