OpenVAS: NVT Description

[Hani Benhabiles <hani.benhabiles () greenbone net>]

Hi list,

I have read some of previous emails about separating some of the 
information that is included in NVT scripts description in order to make 
output parsing and reporting easier and more efficient. I have discussed 
some ideas with Jan and have come up with the following as a start:
* References/URLs/See also: These contain web links that have more 
contextual information about the issue. A suitable name to differentiate 
these references from other references types could be "URL".
As an example, in gb_edirectory_57038.nasl:
References:
http://www.securityfocus.com/bid/57038
http://www.novell.com/products/edirectory/
http://www.novell.com/

Would become:
script_xref(name : "URL" , value 
"http://www.securityfocus.com/bid/57038";);
script_xref(name : "URL" , value 
"http://www.novell.com/products/edirectory/";);
script_xref(name : "URL" , value "http://www.novell.com/";);

* Solution/Fix: These contain information about the issue. After some 
discussion, we have come to think of using script_tag() with a suitable 
tag name.
As an example:

Solution:
An update is available. Please see the references for more
information.

would become something like:
script_tag(name:"solution", value:"An update is available. Please see 
the references for more information.");
Any issues with this ? Ideas on how this could be further improved ? 
Feedback is welcome.
Cheers,
Hani.
_______________________________________________
Openvas-plugins mailing list
Openvas-plugins () wald intevation org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-plugins