6.Īdd an attachment (for example, process trace, log segments, patches, and so forth) while viewing the bug report, if appropriate. If everything goes okay, Bugzilla will show you a copy of your bug report. ■Ĭlick the Commit button at the bottom of the form to file the bug report. Nessus-installer The stand-alone installation script for Nessus. NessusClient the nessus client, for any platform. Nessus nessusd, the UNIX-based nessus client, plug-ins, and the like. 2.Ĭlick Enter new bug report at the base of the Query page or go to /enter_bug.cgi. Log in to your Bugzilla account as just described.
Even if you are unable to solve the problem yourself, your efforts will mean a higher quality bug report. Perhaps the targets aren’t real, but merely part of a LaBrea tarpit (enable plug-in #10796, scan for LaBrea tarpitted hosts, to detect such hosts and flag them as dead). Perhaps you had selected a UDP scan with a large port list (such scans can take up to 24 hours per host). If they are the same, examine the plug-ins or targets themselves for issues you might not have been aware of earlier. If it hangs a second time, check again which plug-ins and targets are active. If it completes successfully, take note of the problem but don’t submit a bug report just chalk up the earlier hang to sunspots, user error, or the like. For example, if nessusd appears to hang during a scan, examine the process list to see if there is a common set of plug-ins running and look at the nessusd message log to see which targets are in the process of being scanned. You can access both from the project’s Bug Tracker homepage.īefore you submit a bug report, first verify that the bug is reproducible and then try to narrow it down. Querying Existing Bug Reportsīugzilla provides two methods for searching bug reports: a simple QuickSearch and a general query. So, if you think you’ve uncovered a bug in Nessus or a related product, first check with Bugzilla to see whether it’s a known issue and, if not, report it using Bugzilla. It reduces duplication of effort by serving as a reference for the user community. It helps project developers coordinate and prioritize their efforts to address bugs. It keeps you abreast of efforts to fix the problem through a series of e-mail alerts. It ensures that your bug report will not be overlooked. It offers several advantages compared to posting a message to one of the mailing lists or e-mailing someone directly: ■
The Nessus Project’s Bug Tracker, located at /, uses the popular Bugzilla software to track bugs (and enhancement requests) in Nessus, its associated plug-ins, the Nessus installer, NessusWX, and Web sites in the domain.
0 kommentar(er)
