I've just pushed up new installers for Peach 2.3.2. This version contains some changes to how debuggers are handled in Windows to resolve some issues several people ran into. Now instead of running the debugger in a thread we spawn off a full process. This fixes some stability issues found when performing file fuzzing of some targets.
This release includes some modules updates, specifically a new PyDbgEng is needed and included in the tree. Additionally for Python v2.5 a new module "multiprocessing" is required (also available in the tree). This is only required for 2.5 as it's included in 2.6.
If you have experienced your file fuzzing stalling out or going slow, upgrade to this release and you should see a marked improvement.
> I've just pushed up new installers for Peach 2.3.2. This version
> contains some changes to how debuggers are handled in Windows to resolve
> some issues several people ran into. Now instead of running the
> debugger in a thread we spawn off a full process. This fixes some
> stability issues found when performing file fuzzing of some targets.
> This release includes some modules updates, specifically a new PyDbgEng
> is needed and included in the tree. Additionally for Python v2.5 a new
> module "multiprocessing" is required (also available in the tree). This
> is only required for 2.5 as it's included in 2.6.
> If you have experienced your file fuzzing stalling out or going slow,
> upgrade to this release and you should see a marked improvement.
> I've just pushed up new installers for Peach 2.3.2. This version
> contains some changes to how debuggers are handled in Windows to resolve
> some issues several people ran into. Now instead of running the
> debugger in a thread we spawn off a full process. This fixes some
> stability issues found when performing file fuzzing of some targets.
> This release includes some modules updates, specifically a new PyDbgEng
> is needed and included in the tree. Additionally for Python v2.5 a new
> module "multiprocessing" is required (also available in the tree). This
> is only required for 2.5 as it's included in 2.6.
> If you have experienced your file fuzzing stalling out or going slow,
> upgrade to this release and you should see a marked improvement.
> When runtime executable is started (and in other occasions), alert
> says:an entry point for _ftol2 function cannot be found in msvcrt.dll.
> (Well, I do not have any MS Visual Studio installed. But I guess Peach
> runtime would use its bin\msvcrt.dll.)
> Tried with C:\peach2.3.2 and C:\peach locations.
> Martin
> On 31 říj, 03:16, Michael Eddington <medding...@gmail.com> wrote:
>> I've just pushed up new installers for Peach 2.3.2. This version
>> contains some changes to how debuggers are handled in Windows to resolve
>> some issues several people ran into. Now instead of running the
>> debugger in a thread we spawn off a full process. This fixes some
>> stability issues found when performing file fuzzing of some targets.
>> This release includes some modules updates, specifically a new PyDbgEng
>> is needed and included in the tree. Additionally for Python v2.5 a new
>> module "multiprocessing" is required (also available in the tree). This
>> is only required for 2.5 as it's included in 2.6.
>> If you have experienced your file fuzzing stalling out or going slow,
>> upgrade to this release and you should see a marked improvement.
I worked around the issue by renaming "peach\bin\iphlpapi.dll" to
iphlpapi_bak.dll. Peach doesn't 't seem to care and the message box went
away. (note: I only did a quick test, allowing peach to go through a couple
iterations of a file fuzzing run)
What does this dll do? It seems to use a different msvcrt.dll than the one
in the peach dir.
-Greg
On Sat, Oct 31, 2009 at 12:49 PM, Michael Eddington <medding...@gmail.com>wrote:
> Hrm, seems on some systems the msvcrt.dll has changed or out of date.
> Tested on Win XP SP3, Vista, and Win7.
> mike
> On 10/31/2009 4:57 AM, Martin Žember wrote:
> > When runtime executable is started (and in other occasions), alert
> > says:an entry point for _ftol2 function cannot be found in msvcrt.dll.
> > (Well, I do not have any MS Visual Studio installed. But I guess Peach
> > runtime would use its bin\msvcrt.dll.)
> > Tried with C:\peach2.3.2 and C:\peach locations.
> > Martin
> > On 31 říj, 03:16, Michael Eddington <medding...@gmail.com> wrote:
> >> I've just pushed up new installers for Peach 2.3.2. This version
> >> contains some changes to how debuggers are handled in Windows to resolve
> >> some issues several people ran into. Now instead of running the
> >> debugger in a thread we spawn off a full process. This fixes some
> >> stability issues found when performing file fuzzing of some targets.
> >> This release includes some modules updates, specifically a new PyDbgEng
> >> is needed and included in the tree. Additionally for Python v2.5 a new
> >> module "multiprocessing" is required (also available in the tree). This
> >> is only required for 2.5 as it's included in 2.6.
> >> If you have experienced your file fuzzing stalling out or going slow,
> >> upgrade to this release and you should see a marked improvement.
> I worked around the issue by renaming "peach\bin\iphlpapi.dll" to
> iphlpapi_bak.dll. Peach doesn't 't seem to care and the message box went
> away. (note: I only did a quick test, allowing peach to go through a couple
> iterations of a file fuzzing run)
> What does this dll do? It seems to use a different msvcrt.dll than the one
> in the peach dir.
> -Greg
> On Sat, Oct 31, 2009 at 12:49 PM, Michael Eddington <medding...@gmail.com>wrote:
>> Hrm, seems on some systems the msvcrt.dll has changed or out of date.
>> Tested on Win XP SP3, Vista, and Win7.
>> mike
>> On 10/31/2009 4:57 AM, Martin Žember wrote:
>>> When runtime executable is started (and in other occasions), alert
>>> says:an entry point for _ftol2 function cannot be found in msvcrt.dll.
>>> (Well, I do not have any MS Visual Studio installed. But I guess Peach
>>> runtime would use its bin\msvcrt.dll.)
>>> Tried with C:\peach2.3.2 and C:\peach locations.
>>> Martin
>>> On 31 říj, 03:16, Michael Eddington <medding...@gmail.com> wrote:
>>>> I've just pushed up new installers for Peach 2.3.2. This version
>>>> contains some changes to how debuggers are handled in Windows to resolve
>>>> some issues several people ran into. Now instead of running the
>>>> debugger in a thread we spawn off a full process. This fixes some
>>>> stability issues found when performing file fuzzing of some targets.
>>>> This release includes some modules updates, specifically a new PyDbgEng
>>>> is needed and included in the tree. Additionally for Python v2.5 a new
>>>> module "multiprocessing" is required (also available in the tree). This
>>>> is only required for 2.5 as it's included in 2.6.
>>>> If you have experienced your file fuzzing stalling out or going slow,
>>>> upgrade to this release and you should see a marked improvement.
I have had the issue when I created an MSI package in order to install
2.3.1 to several machines with group policies. Will try to make use of
workarounds mentioned in thread, thanks...
/Kenta
On Nov 4, 5:40 am, Michael Eddington <medding...@gmail.com> wrote:
> Hrmm, interesting I'll look into it. Not sure what iphlpapi.dll does,
> all the dll's are generated during the py2exe build.
> The msvcrt I included is the copy from my build box, shot in the dark to
> try and fix things.
> So far I haven't been able to reproduce the issue as fresh installs
> don't have the issue.
> mike
> On 11/3/2009 7:00 PM, Greg Foltz wrote:
> > I'm running WinXP SP3 and also got this error.
> > I worked around the issue by renaming "peach\bin\iphlpapi.dll" to
> > iphlpapi_bak.dll. Peach doesn't 't seem to care and the message box went
> > away. (note: I only did a quick test, allowing peach to go through a couple
> > iterations of a file fuzzing run)
> > What does this dll do? It seems to use a different msvcrt.dll than the one
> > in the peach dir.
> > -Greg
> > On Sat, Oct 31, 2009 at 12:49 PM, Michael Eddington <medding...@gmail.com>wrote:
> >> Hrm, seems on some systems the msvcrt.dll has changed or out of date.
> >> Tested on Win XP SP3, Vista, and Win7.
> >> mike
> >> On 10/31/2009 4:57 AM, Martin Žember wrote:
> >>> When runtime executable is started (and in other occasions), alert
> >>> says:an entry point for _ftol2 function cannot be found in msvcrt.dll.
> >>> (Well, I do not have any MS Visual Studio installed. But I guess Peach
> >>> runtime would use its bin\msvcrt.dll.)
> >>> Tried with C:\peach2.3.2 and C:\peach locations.
> >>> Martin
> >>> On 31 říj, 03:16, Michael Eddington <medding...@gmail.com> wrote:
> >>>> I've just pushed up new installers for Peach 2.3.2. This version
> >>>> contains some changes to how debuggers are handled in Windows to resolve
> >>>> some issues several people ran into. Now instead of running the
> >>>> debugger in a thread we spawn off a full process. This fixes some
> >>>> stability issues found when performing file fuzzing of some targets.
> >>>> This release includes some modules updates, specifically a new PyDbgEng
> >>>> is needed and included in the tree. Additionally for Python v2.5 a new
> >>>> module "multiprocessing" is required (also available in the tree). This
> >>>> is only required for 2.5 as it's included in 2.6.
> >>>> If you have experienced your file fuzzing stalling out or going slow,
> >>>> upgrade to this release and you should see a marked improvement.
it's exciting to thing to hear the upgrade news!!
but why there is not dependencies file of Peach 2.3.2 for download?
mike, can you offer me the dependencies file of Peach 2.3.2 .
thanks
On 10月31日, 上午10时16分, Michael Eddington <medding...@gmail.com> wrote:
> I've just pushed up new installers for Peach 2.3.2. This version
> contains some changes to how debuggers are handled in Windows to resolve
> some issues several people ran into. Now instead of running the
> debugger in a thread we spawn off a full process. This fixes some
> stability issues found when performing file fuzzing of some targets.
> This release includes some modules updates, specifically a new PyDbgEng
> is needed and included in the tree. Additionally for Python v2.5 a new
> module "multiprocessing" is required (also available in the tree). This
> is only required for 2.5 as it's included in 2.6.
> If you have experienced your file fuzzing stalling out or going slow,
> upgrade to this release and you should see a marked improvement.
So with the latest releases of Peach I'm releasing them as binary
executables that not longer require Python being installed. The
installers will create a c:\peach with a "bin" folder that actually has
a "peach.exe." I did this to try and make installing easier. For
example, you can just place the peach folder on any machine and Peach
will run with no other software (well you still need windbg for debugging :)
If you still want to use the source version you can get it from SVN
along with the dependencies. Each release is tagged in SVN, so for
example, 2.3.2 would have an SVN root of:
> it's exciting to thing to hear the upgrade news!!
> but why there is not dependencies file of Peach 2.3.2 for download?
> mike, can you offer me the dependencies file of Peach 2.3.2 .
> thanks
> On 10月31日, 上午10时16分, Michael Eddington <medding...@gmail.com> wrote:
>> I've just pushed up new installers for Peach 2.3.2. This version
>> contains some changes to how debuggers are handled in Windows to resolve
>> some issues several people ran into. Now instead of running the
>> debugger in a thread we spawn off a full process. This fixes some
>> stability issues found when performing file fuzzing of some targets.
>> This release includes some modules updates, specifically a new PyDbgEng
>> is needed and included in the tree. Additionally for Python v2.5 a new
>> module "multiprocessing" is required (also available in the tree). This
>> is only required for 2.5 as it's included in 2.6.
>> If you have experienced your file fuzzing stalling out or going slow,
>> upgrade to this release and you should see a marked improvement.
> So with the latest releases of Peach I'm releasing them as binary
> executables that not longer require Python being installed. The
> installers will create a c:\peach with a "bin" folder that actually has
> a "peach.exe." I did this to try and make installing easier. For
> example, you can just place the peach folder on any machine and Peach
> will run with no other software (well you still need windbg for debugging :)
> If you still want to use the source version you can get it from SVN
> along with the dependencies. Each release is tagged in SVN, so for
> example, 2.3.2 would have an SVN root of:
> > it's exciting to thing to hear the upgrade news!!
> > but why there is not dependencies file of Peach 2.3.2 for download?
> > mike, can you offer me the dependencies file of Peach 2.3.2 .
> > thanks
> > On 10月31日, 上午10时16分, Michael Eddington <medding...@gmail.com> wrote:
> >> I've just pushed up new installers for Peach 2.3.2. This version
> >> contains some changes to how debuggers are handled in Windows to resolve
> >> some issues several people ran into. Now instead of running the
> >> debugger in a thread we spawn off a full process. This fixes some
> >> stability issues found when performing file fuzzing of some targets.
> >> This release includes some modules updates, specifically a new PyDbgEng
> >> is needed and included in the tree. Additionally for Python v2.5 a new
> >> module "multiprocessing" is required (also available in the tree). This
> >> is only required for 2.5 as it's included in 2.6.
> >> If you have experienced your file fuzzing stalling out or going slow,
> >> upgrade to this release and you should see a marked improvement.
That's fine. Just as an FYI- Unless you are modifying the core code you
can add additional Publishers, custom types, Fixups, Monitors, etc. with
out changing any code in the Peach tree. Just create a new file
(mystuff.py) and then use the <PythonPath> and <Import> statements in
your pit file to include the code. This also works with the binary version.
This is definitely the recommended method for extending Peach when
possible as other installs can then easily use the created fuzzers. It
also makes it easier to upgrade the Peach instance.
> thanks for your quick reply! I prefer to use the dependencies version,
> causes, I can add my own function in it.
> On 11月14日, 下午10时08分, Michael Eddington <medding...@gmail.com> wrote:
>> So with the latest releases of Peach I'm releasing them as binary
>> executables that not longer require Python being installed. The
>> installers will create a c:\peach with a "bin" folder that actually has
>> a "peach.exe." I did this to try and make installing easier. For
>> example, you can just place the peach folder on any machine and Peach
>> will run with no other software (well you still need windbg for debugging :)
>> If you still want to use the source version you can get it from SVN
>> along with the dependencies. Each release is tagged in SVN, so for
>> example, 2.3.2 would have an SVN root of:
>>> it's exciting to thing to hear the upgrade news!!
>>> but why there is not dependencies file of Peach 2.3.2 for download?
>>> mike, can you offer me the dependencies file of Peach 2.3.2 .
>>> thanks
>>> On 10月31日, 上午10时16分, Michael Eddington <medding...@gmail.com> wrote:
>>>> I've just pushed up new installers for Peach 2.3.2. This version
>>>> contains some changes to how debuggers are handled in Windows to resolve
>>>> some issues several people ran into. Now instead of running the
>>>> debugger in a thread we spawn off a full process. This fixes some
>>>> stability issues found when performing file fuzzing of some targets.
>>>> This release includes some modules updates, specifically a new PyDbgEng
>>>> is needed and included in the tree. Additionally for Python v2.5 a new
>>>> module "multiprocessing" is required (also available in the tree). This
>>>> is only required for 2.5 as it's included in 2.6.
>>>> If you have experienced your file fuzzing stalling out or going slow,
>>>> upgrade to this release and you should see a marked improvement.
> That's fine. Just as an FYI- Unless you are modifying the core code you
> can add additional Publishers, custom types, Fixups, Monitors, etc. with
> out changing any code in the Peach tree. Just create a new file
> (mystuff.py) and then use the <PythonPath> and <Import> statements in
> your pit file to include the code. This also works with the binary version.
> This is definitely the recommended method for extending Peach when
> possible as other installs can then easily use the created fuzzers. It
> also makes it easier to upgrade the Peach instance.
> > thanks for your quick reply! I prefer to use the dependencies version,
> > causes, I can add my own function in it.
> > On 11月14日, 下午10时08分, Michael Eddington <medding...@gmail.com> wrote:
> >> So with the latest releases of Peach I'm releasing them as binary
> >> executables that not longer require Python being installed. The
> >> installers will create a c:\peach with a "bin" folder that actually has
> >> a "peach.exe." I did this to try and make installing easier. For
> >> example, you can just place the peach folder on any machine and Peach
> >> will run with no other software (well you still need windbg for debugging :)
> >> If you still want to use the source version you can get it from SVN
> >> along with the dependencies. Each release is tagged in SVN, so for
> >> example, 2.3.2 would have an SVN root of:
> >>> it's exciting to thing to hear the upgrade news!!
> >>> but why there is not dependencies file of Peach 2.3.2 for download?
> >>> mike, can you offer me the dependencies file of Peach 2.3.2 .
> >>> thanks
> >>> On 10月31日, 上午10时16分, Michael Eddington <medding...@gmail.com> wrote:
> >>>> I've just pushed up new installers for Peach 2.3.2. This version
> >>>> contains some changes to how debuggers are handled in Windows to resolve
> >>>> some issues several people ran into. Now instead of running the
> >>>> debugger in a thread we spawn off a full process. This fixes some
> >>>> stability issues found when performing file fuzzing of some targets.
> >>>> This release includes some modules updates, specifically a new PyDbgEng
> >>>> is needed and included in the tree. Additionally for Python v2.5 a new
> >>>> module "multiprocessing" is required (also available in the tree). This
> >>>> is only required for 2.5 as it's included in 2.6.
> >>>> If you have experienced your file fuzzing stalling out or going slow,
> >>>> upgrade to this release and you should see a marked improvement.
> On 14 Nov, 16:35, Michael Eddington <medding...@gmail.com> wrote:
>> That's fine. Just as an FYI- Unless you are modifying the core code you
>> can add additional Publishers, custom types, Fixups, Monitors, etc. with
>> out changing any code in the Peach tree. Just create a new file
>> (mystuff.py) and then use the <PythonPath> and <Import> statements in
>> your pit file to include the code. This also works with the binary version.
>> This is definitely the recommended method for extending Peach when
>> possible as other installs can then easily use the created fuzzers. It
>> also makes it easier to upgrade the Peach instance.
>>> thanks for your quick reply! I prefer to use the dependencies version,
>>> causes, I can add my own function in it.
>>> On 11月14日, 下午10时08分, Michael Eddington <medding...@gmail.com> wrote:
>>>> So with the latest releases of Peach I'm releasing them as binary
>>>> executables that not longer require Python being installed. The
>>>> installers will create a c:\peach with a "bin" folder that actually has
>>>> a "peach.exe." I did this to try and make installing easier. For
>>>> example, you can just place the peach folder on any machine and Peach
>>>> will run with no other software (well you still need windbg for debugging :)
>>>> If you still want to use the source version you can get it from SVN
>>>> along with the dependencies. Each release is tagged in SVN, so for
>>>> example, 2.3.2 would have an SVN root of:
>>>>> it's exciting to thing to hear the upgrade news!!
>>>>> but why there is not dependencies file of Peach 2.3.2 for download?
>>>>> mike, can you offer me the dependencies file of Peach 2.3.2 .
>>>>> thanks
>>>>> On 10月31日, 上午10时16分, Michael Eddington <medding...@gmail.com> wrote:
>>>>>> I've just pushed up new installers for Peach 2.3.2. This version
>>>>>> contains some changes to how debuggers are handled in Windows to resolve
>>>>>> some issues several people ran into. Now instead of running the
>>>>>> debugger in a thread we spawn off a full process. This fixes some
>>>>>> stability issues found when performing file fuzzing of some targets.
>>>>>> This release includes some modules updates, specifically a new PyDbgEng
>>>>>> is needed and included in the tree. Additionally for Python v2.5 a new
>>>>>> module "multiprocessing" is required (also available in the tree). This
>>>>>> is only required for 2.5 as it's included in 2.6.
>>>>>> If you have experienced your file fuzzing stalling out or going slow,
>>>>>> upgrade to this release and you should see a marked improvement.
|
