Hi all,
macosx_10_4_11.nasl seems to trigger on a host which has been upgraded
from Tiger to Leopard (10.5.2). We aren't using any authentication
during the scan, so it's using purely external factors. Has anyone
else seen this, and is there a good way to eliminate this false
positive?
Thanks,
Erik
_______________________________________________
Plugins-writers mailing list
Plugins-writers@list.nessus.org
http://mail.nessus.org/mailman/listinfo/plugins-writers
macosx_10_4_11.nasl seems to trigger on a host which has been upgraded
from Tiger to Leopard (10.5.2). We aren't using any authentication
during the scan, so it's using purely external factors. Has anyone
else seen this, and is there a good way to eliminate this false
positive?
Thanks,
Erik
_______________________________________________
Plugins-writers mailing list
Plugins-writers@list.nessus.org
http://mail.nessus.org/mailman/listinfo/plugins-writers