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]

Re: NASL 3.0 Documentation

Subject: Re: NASL 3.0 Documentation
Date: Fri, 16 Dec 2005 09:37:57 -0700
Thanks for the reply.  I think I've found what I was looking for.  In
the ntp doc's folder there's a file called ntp_extensions.txt.  There's
an additinal preference called "ntp_short_status".  Still looking at
this documentation it's for Nessus 1.3.x.  Have any changes been made
since then?  I've even looked in my Nessus Network Auditing book and
can't anything new there either.

Thanks,
Dave King


George A. Theall wrote:

On Thu, Dec 15, 2005 at 10:57:40AM -0700, Dave King wrote:

 

Is there current documentation somewhere about Nessus
Transport Protocol somewhere.  
   

...
 

Looking in the nessus_core/docs/ntp/ folder there is some documentation,
   


Other than what you've noted, I'm not aware of any.

 

For example, I was
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.

Btw, keep in mind that NessusClient also works with Nessus 2.x; it's
specific to Nessus3.


George
 


_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>