Re: [Peach] Re: HotFuzz CesarTest Help

[Martin Žember]

Hello,

I am forwarding your questions to the HotFuzz mailing-list (HotFuzz
developers are here).

Unfortunately, I do not remember what is the problem with HotFuzz and
Windows 7. I use it only with Windows XP. Does anyone else know?


Martin

On Wed, Jun 20, 2012 at 5:14 AM, Khairi Habidin
<khairi.a...@gmail.com> wrote:
> Hi,
>  By any chance, have you found the solution to the error? It seems that i am
> facing the same issue as well and i am running with a Windows 7 virtual
> image.
>
>
> On Friday, 15 June 2012 04:00:04 UTC+8, Roy wrote:
>>
>> I hope this is some kind of rookie mistake.  I very recently installed
>> Peach and then HotFuzz on my Windows 7 machine. All appeared to go well (no
>> errors on install_log.txt or installation) except for BIND 9 Install. Error
>> message is "Unable to Create Account for this service." no matter what I
>> tried.
>>
>> I then ran the 1st test case after the install in the User manual: Cesar
>> Test. All went well all the way to the main window. All my screens matched
>> the ones in the User manual.
>>
>> Then, regardless of how I started the test (Start All; Start (each one),
>> etc.) and any changes on the main window, the result was the same.  In the
>> client window, there were several Agent: messages but then the kicker:
>> "FAILED TO START AGENT APPLICATION. Please check if path ...".  This is
>> repeated over all 5 iterations.  The error in the Recording window was "No
>> data were recorded during recording faze(sic). This might be ..." and at the
>> bottom "Error Recording Failed!!!".
>>
>> Is this a Windows 7 thing (I understand that XP is recomended.)?    A BIND
>> thing (failure to create account)?
>>
>> Any help is appreciated.
>
> --
> You received this message because you are subscribed to the Google Groups
> "peachfuzz" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/peachfuzz/-/YIFUULA04dwJ.
>
> To post to this group, send email to peac...@googlegroups.com.
> To unsubscribe from this group, send email to
> peachfuzz+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/peachfuzz?hl=en.

[Martin Žember]

Roy,

what is the output in the Agent windows? Is it the traceback with
"module could not be found"? Can you copy-paste it here?

If your XML configuration files differ from the shipped ones, can you
also send them?

I assume that we talk about the XP installation from now on.


Thanks

Martin


On Mon, Jun 25, 2012 at 5:46 PM, Bethel, Roy E. <rbe...@mitre.org> wrote:
> Martin, Khairi, HotFuzz Team, et al,
>
> We greatly your help.  I have included below the 1st 2 iterations from the Client window for Recording. The other iterations are the same.  The other example tests have the same issue.
>
> I also installed HotFuzz on my XP machine at home. The install went well even including the BIND 9 install.  However, HotFuzz aborted for a different reason.  The Traceback was a bunch of Python calls (which I located).
> The final message was:
> "WindowsError:  [Error 126]   The specified module could not be found."
>
> Please do not hesitate to contact me for any reason.  I will assist in every way possible.
>
> Roy Bethel
> The MITRE Corp.  M/S H407
> 7515 Colshire Drive
> McLean, VA  22102-7539
>    E-mail: rbe...@mitre.org
> SIPRNet: rbe...@wiso.mitre.contractor.army.smil.mil
>   MITRE:  (703) 983-5455
>
> =====================================================================
> ] HotFuzz 1.2.0
> ] Copyright (c) HotFuzz Team
>
> ] Product is built on Peach 2.3.5 DEV Runtime (Copyright (c) Michael Eddington)
>
> ] Peach Agent
>
>  //-> Listening on [9001] with no password
>
> Agent: clientHello()
> Agent: Session ID:  b967cfde-bed7-11e1-a461-180373aea5c0
> Agent: clientHello() all done
> Agent: startMonitor(Named_23)
> code: ppprocess.Process(msg.params)
> Agent: Sending Ack
>
> Agent: onTestStarting()
> Agent: onPublisherCall()
> Process: StartOnCall, starting process!
>
> FAILED TO START AGENT APPLICATION. Please check if the path is correct. Please use absolute path or path relative to hotfuzz main directory
>
> Agent: onTestFinished()
>
> Agent: detectFault()
> Agent: Sending detectFault result [False]
> Agent: stopRun()
>
> Agent: onTestStarting()
> Agent: onPublisherCall()
> Process: StartOnCall, starting process!
> FAILED TO START AGENT APPLICATION. Please check if the path is correct. Please use absolute path or path relative to hotfuzz main directory
>
> Agent: onTestFinished()
> =========================================================================

[Bethel, Roy E.]

[Bethel, Roy E.]

Martin,

Since the XP machine is at home, I will have to do that this afternoon or tonight and send you the results tomorrow. I will send you the output for all 3 windows. Please let me know if you need anything else.

Everything including all *.xml files is the same as "out of the box". No changes. Just like for Win 7, the same error occurred for all HotFuzz example tests.

We would still be interested in resolving the issues for Win 7 since that is now the only "officially" supported OS for my company. Unofficially, we could probably get by with XP if that were the only option.

Thanks to everyone for your help.

Roy Bethel
The MITRE Corp. M/S H407
7515 Colshire Drive
McLean, VA 22102-7539
E-mail: rbe...@mitre.org
SIPRNet: rbe...@wiso.mitre.contractor.army.smil.mil
MITRE: (703) 983-5455

[Pavel Kankovsky]

On Mon, 25 Jun 2012, Bethel, Roy E. wrote:

> FAILED TO START AGENT APPLICATION. Please check if the path is correct. Please use absolute path or path relative to hotfuzz main directory

It seems Process._StartProcess in Peach/Agent/ppprocess.py fails but
someone (wink, wink) did not bother to provide a better error message.

Try adding
import traceback
traceback.print_exc(10)
after
except:
print "FAILED TO START AGENT APPLICATION. ..."

It will not make it work but it might provide a better explanation of the
error and its causes.

--Pavel Kankovsky aka Peak

[Bethel, Roy E.]

Martin,

These are the files for the 3 windows for the CesarFTP Test under XP.

The Client and the Server are the same. There is only a single (error) message for the Recording.

Again, thanks for your help.

Roy Bethel
The MITRE Corp. M/S H407
7515 Colshire Drive
McLean, VA 22102-7539
E-mail: rbe...@mitre.org
SIPRNet: rbe...@wiso.mitre.contractor.army.smil.mil
MITRE: (703) 983-5455

-----Original Message-----
From: Bethel, Roy E.
Sent: Tuesday, June 26, 2012 8:56 AM
To: 'Martin Žember'
Cc: hotfuzz-project; Khairi Habidin; Patterson, James
Subject: RE: [Peach] Re: HotFuzz CesarTest Help

Martin,

Since the XP machine is at home, I will have to do that this afternoon or tonight and send you the results tomorrow. I will send you the output for all 3 windows. Please let me know if you need anything else.

Everything including all *.xml files is the same as "out of the box". No changes. Just like for Win 7, the same error occurred for all HotFuzz example tests.

We would still be interested in resolving the issues for Win 7 since that is now the only "officially" supported OS for my company. Unofficially, we could probably get by with XP if that were the only option.

Thanks to everyone for your help.

Roy Bethel
The MITRE Corp. M/S H407
7515 Colshire Drive
McLean, VA 22102-7539
E-mail: rbe...@mitre.org
SIPRNet: rbe...@wiso.mitre.contractor.army.smil.mil
MITRE: (703) 983-5455

-----Original Message-----
From: Martin Žember [mailto:zem...@gmail.com]

Sent: Tuesday, June 26, 2012 7:42 AM
To: Bethel, Roy E.
Cc: hotfuzz-project; Khairi Habidin; Patterson, James

[Bethel, Roy E.]

Peak,

Inserted the lines in Peach/Agent/ppprocess.py. Saved. Opened
HotFuzz. Ran CesarTest.
Exactly the same result. Hmmmmm. (Note: I primarily use MatLab.)

I noticed all the *.py in Peach/Agent had *.pyc counterparts and the dates
were the same date I installed HotFuzz.
Brilliant deduction (I can also recite the alphabet and count to 9. I need
to get to 10.):
The *.py were/need to be re-compiled to *.pyc. HotFuzz executes on
the *.pyc.

It would seem there is a compile procedure somewhere that needs to be run.
I don't trust myself to figure it out.

Roy Bethel
The MITRE Corp.  M/S H407
7515 Colshire Drive
McLean, VA  22102-7539
    E-mail: rbe...@mitre.org
SIPRNet: rbe...@wiso.mitre.contractor.army.smil.mil
   MITRE:  (703) 983-5455

-----Original Message-----
From: Pavel Kankovsky [mailto:pe...@mbox.troja.mff.cuni.cz]
Sent: Tuesday, June 26, 2012 7:50 PM
To: Bethel, Roy E.
Cc: hotfuzz-project; Khairi Habidin; Patterson, James

[Martin Žember]

Hi Roy,

in case the .pyc file is not regenerated from the source by itself,
you can force it by simply deleting it. You will see if it helps.

I still do not know anything about the issue with Windows 7.

Regarding XP, this line in your backtrace is interesting:

File "C:\HotFuzz\Shark_libs\tm_export.py", line 571, in <module>
_libs["tm_export.dll"] =
load_library(sys.path[0]+"\\Shark_libs\\libraries\\tm_export.dll")

It seems that the file cannot be found. Is it there? (In
C:\HotFuzz\Shark_libs\libraries\\tm_export.dll?)

Martin

[Martin Žember]

Roy,

besides the existence of the DLL file, I have one other question - is
it a 64-bit Windows by chance?

Martin

[Pavel Kankovsky]

On Wed, 27 Jun 2012, Bethel, Roy E. wrote:

> Inserted the lines in Peach/Agent/ppprocess.py. Saved. Opened
> HotFuzz. Ran CesarTest.
> Exactly the same result. Hmmmmm. (Note: I primarily use MatLab.)
>
> I noticed all the *.py in Peach/Agent had *.pyc counterparts and the dates
> were the same date I installed HotFuzz.

*.pyc files are compiled (sort of) versions of Python scripts. They are
generated and updated automatically by the Python runtime. As Martin
wrote, you can delete them and force Python to recompile corresponding
source code files. But it should never be necessary as Python is supposed
to keep them up to date.

I am at a loss that your changes to ppprocess.py are ignored (despite
having encountered a problem that seemed to be identical to yours as
described in my postscriptum).

You can try the following things:

1. Modify the original error message ("FAILED TO START..."). Run HotFuzz.
Examine ppprocess.pyc and check whether it was updated and whether
it contains the modified message.

2. Make sure all lines are indented correctly because program structures
are determined by indentation in Python and even minute differences
(spaces instead of tabs) are important. You can use an editor included in
PythonWin GUI (bundled with ActiveState Python).


PS: I am sorry it took me so long to respond. Various circumstances
conspired against me; here is a partial list preserved for the benefit,
education, and amusement of posterity:

1. My installation of HotFuzz succumbed to some kind of bitrot and
stopped working. Every time a fuzzing process was started it crashed in
hf_dissect_init (?) until I removed a bunch of various software
packages and did a complete reinstall of HotFuzz and its dependencies.

2. I wanted to reproduce your problem with *.pyc files. I made proposed
changes to ppprocess.py, broke CesarTest configuration (so as to make it
unable to start a program), started fuzzing... and my changes were
ignored. It regenerated ppprocess.pyc every time I deleted it or changed
ppprocess.py and its contents corresponded to the modified source code but
it kept behaving as if the code had not been changed at all. It turned out
I had broke the wrong part of CesarTest (server instead of client) and the
code where an exception occurred was different from the code I modified
(ppmonitor.py instead of ppprocess.py).

Unfortunately, this does not help to explain your problems. I checked the
output you sent earlier and your exception occurred in ppprocess.py.


--Pavel Kankovsky aka Peak