Closed dvppvd closed 1 year ago
This is unlikely a bug / issue in openvas-nasl
but just a matter to "correctly" call openvas-nasl
on the command line.
Examples / additional background info on this topic have been given in the past e.g. here:
https://forum.greenbone.net/t/how-to-test-a-single-nasl-via-the-command-line/8131/3
Hi @cfi-gb, I rebuilt openvas-scanner
with the source tag v22.4.0 and didn't encounter the issues above.
@dvppvd This info was missing so far that a previous version of openvas-nasl
worked. Could you please add this info to the initial report so that the team working on this topic is able to see that immediately.
@dvppvd This info was missing so far that a previous version of
openvas-nasl
worked. Could you please add this info to the initial report so that the team working on this topic is able to see that immediately.
My mistake, I updated the report.
Expected behavior
openvas-nasl
works properly.Actual behavior
When running the VT
find_service.nasl
withopenvas-nasl
, no services are detected, running withopenvas
is fine.Steps to reproduce
find_service.nasl
against a host withopenvas-nasl
.GVM versions
ospd-openvas: built from latest stable source (HEAD: 71e568611201556b404c46de15c26bae75cb457a).
Note: the tool worked properly in the previous versions such as v22.4.0.