Sorry, should have responded back. I believe so - the key problem appeared to be protocol changes, (addition of 'CLIENT <|> GO ON <|> CLIENT') and the change form scriptid to script oid.
I haven't had time to revisit this and to rejig the various test harnesses we have yet for these changes (the scriptid to script oid is a bit of a pain). Thanks, Thomas Jan-Oliver Wagner wrote: > Hi Thomas, > > On Friday 23 July 2010 17:25:17 Thomas Reinke wrote: >> Has anyone noted explicitly whether the port_range setting is >> working in OpenVAS? Specifically, we have found that setting >> port_range in the openvassd.conf file works as advertised, >> but if one tries to override that within the OTP protocol, >> the override doesn't work, resulting in an inability to >> control the ports scanned in things like openvas_tcp_scanner >> ... > > have the answers helped you to solve your problem? > > Best > > Jan > _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
