Re: "unscanned ports closed" now appears to be broken?
Jason Haar <[email protected]>
| Newsgroups | gmane.comp.security.nessus.general |
|---|---|
| Organization | Trimble Navigation Ltd. |
| Message-ID | <[email protected]> |
Renaud Deraison wrote: > > You probably enabled the "portscanner" plugin#34220 which causes some > re-ordering and causes this bug. Hmm # grep 34220 .nessusrc 34220 = no I don't think that's it? > > 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 use nessusd for much more that just this "windows lite" scan - will that global reject rule break more thorough scans? Thanks -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus