links between NVTs

[cfi]

Hi,

as pointed out via IRC please have a look at the “Golden Rules” and “How to write a product detection VT” parts of the following high level overview / description VT Development - Vulnerability Tests - Greenbone Community Forum which should answer most of the questions.

A short sum-up to your related questions in this thread:

@manasa-ummadi

how are different nasl scripts linked to each other?

Via the script_dependencies() as well as via the script_require_keys() and/or script_mandatory_keys() described in the linked article.

@manasa-ummadi

there is a difference between the two openvas scans that include group of families and a single family? does families also depend on each other? why?

Families are not relevant for the VT and are only used to allow the end user to create own scan configurations with VTs of specific families.

@manasa-ummadi

the result in the log is found by b.nasl script. how can we know that they are linked

Via the script_dependencies() described above.

@manasa-ummadi

and how to know how many scripts a.nasl depends on?

You would need to follow the script_dependencies() of each .nasl file on your local file system and grep through your plugins folder so see the dependencies.