Le 11/06/2012 13:10, Sebastien Aucouturier a écrit :
I can't tell you about your commit, and before, as this is my first
run with openvas-nasl 5.0 and nmap.nasl,
I used the openvas Source Code tarball from the website,
NVT version is 201206071609
NMAP 5.51.6
port range : the default one
i do the same test with openvas 4.0.6 (same NVT-FEED, same NMAP
Version and Port-Range) on another machine, and it goes OK.
So i run other nasl scripts through openvas-nasl-5.0.1 and each
segfault so NVT or nmap are not the source of this behaviour.
If you can't reproduce in your env, i will dig it on my host.
BR
i got more info,
the faulty is in get_plugin_preference function (misc/plugutils.c)
with the following code :
char *plug_name = nvti_name (arg_get_value (desc, "NVTI"));
arg_get_value (desc, "NVTI") return null ...
so nvti_name segfault ;-)
because :
gchar *
nvti_name (const nvti_t * n)
{
return (n->name);
}
--
| Sébastien AUCOUTURIER | Software Design Engineer Lead
| ITrust | 55 rue l'Occitane BP 67303 31673 LABEGE CEDEX
| Email: s.aucoutur...@itrust.fr
| Fixe Sdt. 05.67.34.67.80 | Fax. 09.80.08.37.23
| IT Security Services & SaaS Editor
_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-devel