Re: "unscanned ports closed" now appears to be broken?
Renaud Deraison <[email protected]>
| Newsgroups | gmane.comp.security.nessus.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Jason, On Sep 24, 2008, at 3:05 AM, Jason Haar wrote: > Hi there > > I've just noticed our scheduled nessus scans aren't getting the > Windows > results they normally return anymore. > You probably enabled the "portscanner" plugin#34220 which causes some re-ordering and causes this bug. In the short term, you should disable it if you want 'unscanned ports as closed to work'. Another option would be to keep it enabled, to disable the option "consider unscanned ports as closed" and edit nessusd.rules to prevent connecting to the ports you do not want to connect to. ie: reject 0.0.0.0/0:1024-65535 would forbid nessusd from connecting to these ports. We'll fix that problem in 3.2.2. Thanks, -- Renaud _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus