WinAppDbg version 1.2 is out!

What is WinAppDbg?
==================

The WinAppDbg python module allows developers to quickly code instrumentation
scripts in Python under a Windows environment.

It uses ctypes to wrap many Win32 API calls related to debugging, and provides
an object-oriented abstraction layer to manipulate threads, libraries and
processes, attach your script as a debugger, trace execution, hook API calls,
handle events in your debugee and set breakpoints of different kinds (code,
hardware and memory). Additionally it has no native code at all, making it
easier to maintain or modify than other debuggers on Windows.

The intended audience are QA engineers and software security auditors wishing to
test / fuzz Windows applications with quickly coded Python scripts. Several
ready to use utilities are shipped and can be used for this purposes.

Current features also include disassembling x86 native code (using the open
source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
processes simultaneously and produce a detailed log of application crashes,
useful for fuzzing and automated testing.


Where can I find WinAppDbg?
===========================

The WinAppDbg project is currently hosted at Sourceforge, and can be found at:

    http://winappdbg.sourceforge.net/

Its also hosted at the Python Package Index (PyPi):

    http://pypi.python.org/pypi/winappdbg/1.2


Replies to this exploit:

From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?


From: Jared DeMott jdemott@crucialsecurity.com
Sent: Tue 16. Jun 2009 14:26
Mario Alejandro Vilas Jerez wrote:
> What is WinAppDbg?
> ==================
> 
> The WinAppDbg python module allows developers to quickly code instrumentation
> scripts in Python under a Windows environment.

Can you compare/contrast with pydbg so I can understand why I might want
to give it a try?  Do you have a fuzzing platform like Sulley for it as
well?  Thx!
Jared


> 
> It uses ctypes to wrap many Win32 API calls related to debugging, and provides
> an object-oriented abstraction layer to manipulate threads, libraries and
> processes, attach your script as a debugger, trace execution, hook API calls,
> handle events in your debugee and set breakpoints of different kinds (code,
> hardware and memory). Additionally it has no native code at all, making it
> easier to maintain or modify than other debuggers on Windows.
> 
> The intended audience are QA engineers and software security auditors wishing to
> test / fuzz Windows applications with quickly coded Python scripts. Several
> ready to use utilities are shipped and can be used for this purposes.
> 
> Current features also include disassembling x86 native code (using the open
> source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
> processes simultaneously and produce a detailed log of application crashes,
> useful for fuzzing and automated testing.
> 
> 
> Where can I find WinAppDbg?
> ===========================
> 
> The WinAppDbg project is currently hosted at Sourceforge, and can be found at:
> 
>     http://winappdbg.sourceforge.net/
> 
> Its also hosted at the Python Package Index (PyPi):
> 
>     http://pypi.python.org/pypi/winappdbg/1.2
> 
> 
> 



From: Mario Alejandro Vilas Jerez mvilas@gmail.com
Sent: Tue 16. Jun 2009 15:45
Basically its got some different features than PyDbg and a more
complete documentation. If you have an *existing* project built upon
PyDbg its probably not worth switching (unless youve hit some very
bad problem with it) but I believe its better for newer projects, as
this new library is more flexible and scalable.

It doesnt have a fuzzing platform like Sulley. It does however have
some tools that can be useful when fuzzing, particularly one that
attaches to a program as a debugger and logs the crashes it finds,
using some simple heuristics to avoid logging the same crash twice.

Let me know if you decide to give it a try, Ill help in anything I can :)

Cheers,
-Mario

On Tue, Jun 16, 2009 at 3:26 PM, Jared
DeMott<jdemott@crucialsecurity.com> wrote:
> Can you compare/contrast with pydbg so I can understand why I might want
> to give it a try?  Do you have a fuzzing platform like Sulley for it as
> well?  Thx!
> Jared

--=20
HONEY: I want to=85 put some powder on my nose.
GEORGE: Martha, won=92t you show her where we keep the euphemism?