Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: port scan and plugin selection |
|---|---|
| Date: | Thu, 28 Jun 2007 23:18:44 +0200 |
Le Thu, 28 Jun 2007 17:03:15 -0400, Will Cladek <william.cladek@nrl.navy.mil> a écrit :
How does the port scan portion of Nessus affect the plugins used? Are plugins only run against ports that are found to be open?
No, most plugins are also run against a default port. Anyway, find_service only run on open ports, and service identification is necessary for many plugins. Disabling all port scanners is definitely a bad idea.
If port scanning is disabled, are all plugins run by default? How does the "Safe checks" option relate to this?
There is no direct relationship in either case. _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | port scan and plugin selection, Will Cladek |
|---|---|
| Next by Date: | something about the plugins.xml., steven zhuang |
| Previous by Thread: | port scan and plugin selection, Will Cladek |
| Next by Thread: | Re: port scan and plugin selection, Will Cladek |
| Indexes: | [Date] [Thread] [Top] [All Lists] |