Hello,
My mail concerns the configuration of Nessus client v3.0. I have updated
it, from Nessus Client v1.0, and the currently installed OS is openSuSE
10.3. Both server and client are under the path of (/opt/nessus/sbin for
the nessusd) and (/opt/nessus/bin for the NessusClient).
I have placed the .nessusrc file under the path /home/user/IP
Security/tools. Under the same path I have extracted all the rest of the
tools, like nmap4.23, amap5.2, hydra, ettercap, nikto2.00, and
sctp-scan.
In the options tab of the client, I get the following in the window:
Nessus SNMP scanner
Nessus TCP scanner
Netstat 'scanner'
Nmap (NASL wrapper)
Ping the remote host
SYN scan
Amap (NASL wrapper)
Scan for LaBrea tarpitted hosts
I check all of them, except the last one. So, into the nessus plugins I
have amap.nasl, nmap.nasl and the four executable .nes files. However,
in the advanced tab of NessusClient v3.0, I don't get the following
fields in correspondence to the Prefs tab of the NessusClient v1.0.
These fields are:
Amap (NASL) wrapper
Cleartext Protocol settings
Do not scan fragile devices
Nessus TCP scanner
Nikto (NASL) wrapper
Nmap (NASL) wrapper
So, do I get fewer fields due to a wrong configuration? Moreover is
there a general rule of how can I implement 3rd party tools, (except
from Nikto), like PROTOS, hydra or sctp-scan, into the Nessus? Thanks in
advance for your feedback.
P.S: I'm referring to the custom policy and not the Microsoft patches
policy.
Best Regards,
Konstantinos Tsirgogiannis
Nokia Siemens Networks S.A
COO SCA Perfect Voice Fixed
R&D Centre Athens, XSWCD1
12, Promitheos str.
GR-145 64 N. Kifisia, Athens
Greece
Tel: (+30) 21 06 24 76 99
<mailto:konstantinos.tsirgogiannis@nsn.com>
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
