I'm trying a bunch of scans so that I can get familiar with the over all nessus process.

I've got a situation that I don't understand and maybe someone could shed a little light on this for me.

A lot of the scans that I'm trying to run call out smb_enum_services.nasl as a dependency.

When I run my scans on one client everything runs fine and I get the expected results.

However the next client that I scan, which has a similar configuration does not scan as I would expect.

I put some of my crude debug in the function svcopenscmanager in smb_enum_services.nasl to try to see what might be happening. (see below)

***********************
function svcopenscmanager(
{
.........
 if(!r)return(FALSE);
 #if(strlen(r) < 100)return(FALSE);
 if(strlen(r) < 104)
{
# My Debug
report = "strlen two short";
security_hole(data:report);
exit(0);
}
 #display("hu\n");
 #
 # extract the handle
 #
 hdl = "";
 i = 0;
 for(i=0;i<21;i=i+1)
  {
#   display(hex(ord(r[83+i])), " ");
  hdl =  string(hdl, raw_string(ord(r[83+i])));
  }
# display("\n");
 return(hdl);
}
****************************

So what I get when things fail is that the return string (r) is too short as security hole! (my crude way of DEBUG) My main question is why am I not getting the right size value and what should it be? (I also printed r out as part of the report string and id did not help me)

Also if I uncomment the calls to the method 'display()' where are the values displayed. I looked in the logs but did not see anything.

Is there a way to get a better handle on what's going on, or am I heading in the right direction?

Thanks for any help.

Mike



_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to