Which plugins are you using? So far, it seems you've made it as far as I have with the included plugins. If you search in your openvasd log directory (I think /usr/share/openvas/var/log or something similar) the error log may show the scan quit with a SIGSEGV error. Once I cleaned out the default plugins (wiped out everything in the plugins directory) and ran the openvas-nvt-sync command, it pulls in only the new and approved plugins. From there, scans can complete and vulnerabilities will be listed.
This is what happened for me, anyway. Not sure if it applies in your case or not... On Wed, Aug 20, 2008 at 2:42 PM, Saulo Medeiros de Araújo <[EMAIL PROTECTED] > wrote: > Folks, > > Now i got another problem. The openvas-client doesn't get any > information/issues/vulnerabilities from the targets. I created two users for > openvas-client, and set those following rules for witch one: > > # Login : saulo > # Password : *********** > # > # Rules : > # accept client_ip > # accept 10.0.0.0/16 > # default deny > # > # > # Is that ok? (y/n) [y] y > # user added. > > > # Login : admin > # Password : *********** > # > # Rules : > # > # > # Is that ok? (y/n) [y] y > # user added. > > > But with both users openvas-client doens't get any information. > > Thanks for any help. > > Cheers! > > _______________________________________________ > Openvas-discuss mailing list > [email protected] > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > >
_______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
