If I were you I'd try to do it with SSL disabled, that way you can tell
if it's SSL or something else that's causing the problems. Can you log
into the Nessus server from that windows box using a gui client? There
may be some gotchas using Net::Nessus on Windows, I've only used it on
Linux so I can't be sure, I'm happy to help where I can though.
Laters,
Dave King
Wagner, Chris (GEAE, CBTS) wrote:
I just spent a day getting the Net::Nessus* perl stuff working. I used
Net::Nessus::Scanlite and was able to connect to the new 3.0 server and scan
something. So that works. Right now I'm trying to get it working from a CGI
app. That's not going so well. It complains "Nessus login failed 1: Protocol
error < NTP/1.2 >". It's using SSL. But the exact same code works when called
from the command line. Apache(Win32) probably can't do something since it's
running as SYSTEM. Any ideas?
PS: Thanks for mentioning that, Net::Nessus* is just what I need!
"George A. Theall" wrote:
debugging a program that used Net::Nessus recently and I wanted to make
sure it was acting like other nessus clients, so I sniffed the traffic
between the client and the server. I noticed that NessusClient uses a
shorter message syntax. Is this documented anywhere?
Shorter than what -- Net::Nessus or the unix-based client? I admit I
haven't looked at Net::Nessus for a long time and forget its specifics,
but grepping NessusClient/nessus/*.c and nessus-core/nessus/*.c for
network_printf shows the two clients use much the same NTP calls.
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
