2.0.7 doesn't fix it. I believe it is an open issue. Steps I have taken to track this down are: (since you may want to validate for yourself to see if your results are the same)
+ upgrade to latest nessus + upgrade to latest plugins + disable all tests *except* hydra + create text files for accounts and passwords + start "snooping" traffic between my nessusd machine and my target + tail -f the nessus log + run nessus + watch the (lack of) hydra traffic For me the difinitive one is the network trace. The nessus logs *could* be lying to me, (or I could misinterpret them) but if I am "brute-forcing" a service, I should be seeing specific traffic to that service on my target. If not, it isn't happening. Jim > -----Original Message----- > From: Crow, Owen [mailto:[EMAIL PROTECTED] > Sent: Monday, July 21, 2003 1:49 PM > To: [EMAIL PROTECTED] > Subject: Trouble using Hydra: Finished too quickly > > > Server OS: Redhat 7.2 > Nessus Server: 2.0.7 > > Client OS: Windows XP or Redhat 7.2 > Nessus Client: NessusWX 1.4.4 or native-client 2.0.7 > > I've seen other posts like this but they didn't seem to have > a solution > other than upgrade to 2.0.7. > > I created a users and a words file which cracks one of my > Windows systems > (using SMB) using Hydra 2.2 (from > http://packetstorm.digital-network.net/groups/thc/). When I > try to use this > same combo with Nessus the plugin exits in 0.019 seconds > without cracking > anything. > > nessus.dump doesn't have anything useful in it and > nessus.messages just has > the start and stop messages, no errors. Are there any other steps for > debugging? > > Thanks, > Owen Crow > Systems Programmer (Unix) > BMC Software, Inc. > >
