Thus spake Renaud Deraison ([EMAIL PROTECTED]):
> If you enable the option "safe checks" you can scan your network with no
> fear, as it will just rely on the banner.
I have a semi-unrelated question/problem. When I use nasl directly
to test a specific host that I know is vulnerable to this bug, I get
this:
# nasl -t 192.168.0.1 apache_chunked_encoding.nasl
apache_chunked_encoding.nasl : Warning : evaluating unknown variable - \
description
Success
But when I use the nessus gui (with only the apache chunk scan enabled
and with safe checks disabled), the port scan tells me that something is
listening on port 80, but the host comes up clean in the nessus report.
I'm baffled. Can anyone shed any light on this?
I'm running nessusd 1.2.2 on Solaris 5.8 and a 2.4.xx linux system, and
they both exhibit this problem.
Thanks!
David
