Did you report the bug to HP (or who ever wrote that ITO agent)?
Not yet, as I'm trying to figure out what's really going on.
Can you reproduce the communication of the
DDI_Directory_Scanner.nasl script by hand and still kill it?
I can try to do this, however, I am not really familiar with nasl
scripting yet. Any guidance would be appreciated. I read through the
script, but am not totally positive what everything is doing.
Possibly use NetCat or something like that to connect?
If you can reproduce the issue without nessus and HP is not
willing to wok the problem you may considere posting the bug
on bugtraq. But for now I recommend you try to get HP to wok
on it first.
I will go this route if necessary, but I think I need to prove out
what's going on...
Thanks,
Chris
*******************************
The information contained in this message may be privileged and/or confidential
and
protected from disclosure. If the reader of this message is not the intended
recipient,
or an employee or agent responsible for delivering this message to the intended
recipient,
you are hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited. Note that any views or opinions presented
in this
message are solely those of the author and do not necessarily represent those
of Ameren.
All emails are subject to monitoring and archival. Finally, the recipient
should check
this message and any attachments for the presence of viruses. Ameren accepts no
liability
for any damage caused by any virus transmitted by this email. If you have
received this in
error, please notify the sender immediately by replying to the message and
deleting the
material from any computer. Ameren Corporation
*******************************
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
