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.




Network Security Nessus-Users
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: Nmap (NASL Wrapper) not generating correct nmap command-line

from [Michel Arboi] Network Security [Permanent Link]
Subject: Re: Nmap (NASL Wrapper) not generating correct nmap command-line
Date: Sun, 22 Jan 2006 15:54:05 +0100 
On Sun Jan 22 2006 at 14:15, Michael Scheidell wrote:


I don't disagree on the nmap wrapper issue, if a user, unfamiliar with
nessus uses it on a scan they can easily rob the resources form the
nessus scanner.


That's why we should probably restrict the script to the import
function.


As for netstat, snmp, these (hopefully) won't work in most cases
(without really crappy security on the host)


netstat can work through a SSH account, which does not create any
security hole.


Point is, tcp_wrapper and syn_scan won't give you al list of udp ports.


No. Both are TCP scanners, and they run in a bounded time, whatever the
conditions.


If someone familiar with nmap scans needs a udp port scan, they will
need to be aware of how to identify all the false positives associated
with many udp scans.


Another point is that Nessus does not need or use results from UDP scanners.
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
[More with this subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  RE: Nmap (NASL Wrapper) not generating correct nmap command-line, Michael Scheidell
Next by Date:  Re: NessusClient - unix socket support? (and NBE import?), Jan-Oliver Wagner
Previous by Thread:  RE: Nmap (NASL Wrapper) not generating correct nmap command-line, Michael Scheidell
Next by Thread:  Nessus report temporary files?, Jon Macfarlane
Indexes:  [Date] [Thread] [Top] [All Lists]