> > 1) Is nessus doing the match on the "nmap --version" string or the > > header while nmap is running?? > > Not when it is running, just when the plugin is initializing. > (BTW, there is a kind of cache, maybe you need to "touch" > nmap_wrapper.nes)
"touch"ing the nmap_wrapper.nes didn't make a difference either. Looking into the binary didn't reveal much either. > > 2) Is Nessus doing doing a regex match on this string or a string > > compare? > > sscanf ~ String compare. > > The Nmap plugin is still not showing up in either NessusWX > or in the > > native Xwindows client. > > Then the problem is elsewhere. Is nmap in $PATH for the user > who runs nessusd? Yes, nmap is in the path. You asked this already. ;) The hex edit on Nmap with a recompile of nessus did the trick.... Port scans are back! IMPORTANT NOTICE: This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you have received this message in error, you are hereby notified that we do not consent to any reading, dissemination, distribution or copying of this message. If you have received this communication in error, please notify the sender immediately and destroy the transmitted information.
