You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the PyDbg-based DebuggerThreadPydbg procmon thread was orphaned last year when the project made the switch to full Python 3, the target-based process monitor component is limited to the DebuggerThreadSimple type unless running an older version of Python on the target machine.
I propose the project adopt the Vivisect framework's Vtrace library (https://github.com/vivisect/vivisect) in order to re-obtain the debugger functionality lost with PyDbg. I've already made the switch and have the requisite files available in my own repo (https://github.com/hippo-pat-amus/boofuzz_vtrace), and have tested the new DebuggerThreadVtrace type on both Windows and Linux target platforms.
Use-Case
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Proposal
As the PyDbg-based DebuggerThreadPydbg procmon thread was orphaned last year when the project made the switch to full Python 3, the target-based process monitor component is limited to the DebuggerThreadSimple type unless running an older version of Python on the target machine.
I propose the project adopt the Vivisect framework's Vtrace library (https://github.com/vivisect/vivisect) in order to re-obtain the debugger functionality lost with PyDbg. I've already made the switch and have the requisite files available in my own repo (https://github.com/hippo-pat-amus/boofuzz_vtrace), and have tested the new DebuggerThreadVtrace type on both Windows and Linux target platforms.
Use-Case
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: