Re: Is there any algorithm/mechanism on plugin...
Ron Gula <[email protected]>
| Newsgroups | gmane.comp.security.nessus.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Kevin, Some of these topics we have blogged about. For example, the OS ID fingerprinting link is: http://blog.tenablesecurity.com/2007/05/enhanced_operat.html There are also several white papers about Nessus and Tenable technology here: http://www.nessus.org/whitepapers/ The best way to learn about what a plugin does is to read the code. Ron Kevin Chak wrote: > Hi, > > For the plugins to check vulnerabilities, is there any algorithm/mechanism behind? For example, I saw some of the plugins dealing with HTTP server would have httpver.nasl and http_login.nasl as the dependencies. Does this like a mechanism for checking HTTP server, which run few specific scripts at the beginning? How about the others? I would like to know about the mechanism that dealing with web server, os identification, patches, and service identification. > > > Thanks for your helps, > Kevin > _________________________________________________________________ > Back to work after baby–how do you know when you’re ready? > http://lifestyle.msn.com/familyandparenting/articleNW.aspx?cp-documentid=5797498&ocid=T067MSN40A0701A > > > ------------------------------------------------------------------------ > > _______________________________________________ > Nessus mailing list > [email protected] > http://mail.nessus.org/mailman/listinfo/nessus _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus