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: DOT-NESSUS FILE

Subject: Re: DOT-NESSUS FILE
Date: Wed, 23 Jul 2008 09:32:10 -0400
Hi John,

I haven't looked into this nor have I asked anyone at Tenable to look
into it. You may be taking advantage of some implementation issues and
if an application that processes the .nessus file is expecting to run
into the <Targets> element right after the <NessusClientData>, they
could have errors.

I don't forsee any coding changes to the Nessus Client that would impact
your modifications if you use them locally, but at the same time, we're
not adding a QA step that makes sure your modifications aren't broken
in the future or modifying the official XSD and file format.

Ron Gula
Tenable Network Security

John Scherff wrote:
My question: will this continue to be the behavior in the future?

________________________________

From: nessus-bounces@list.nessus.org
[mailto:nessus-bounces@list.nessus.org] On Behalf Of John Scherff
Sent: Monday, July 21, 2008 6:12 PM
To: nessus@list.nessus.org
Subject: DOT-NESSUS FILE


Tenable Team,
 
I was pleasantly surprised to find out that extraneous XML is not
stripped out of the dot-nessus file by the scanner.  I plan to create a
new node called <Directives> (a sibling to <Policies>) and beneath that
will be configuration items of my own which will be consumed by
post-scan handlers (e.g., scripts that convert and email the scan
results).  For example:
 
<?xml version="1.0"?>
<NessusClientData>
  <Directives>
    <Directive>
      <name>outputFormats</name>
      <value>html;nbe</value>
    </Directive>
    <Directive>
      <name>emailRecipients</name>
      <value>jscherff@24hourfit.com,deraison@nessus.org</value>
    </Directive>
    <Directive>
      <name>attachResults</name>
      <value>no</value>
    </Directive>
    <Directive>
      <name>stripInfos</name>
      <value>yes</value>
    </Directive>
  </Directives>
  <Targets>
    ...
  </Targets>
  <Policies>
    <Policy passwordsType="Linux">
      <policyName/>
      <policyComments/>
      ...
</NessusClientData>
 
My question: Is it by accident or design that unused XML is ignored and
left untouched by the nessus, and will this continue to be the behavior
in the future?
 
Thanks,
 
John Scherff
Information Security and Storage Manager
24 Hour Fitness
o: 760-918-4485
c: 760-351-6946
e: jscherff@24hourfit.com
 
The code of competence is the only system of morality that's on a gold
standard. -Ayn Rand
 
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

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