Closed Rich5 closed 7 years ago
as of the latest commit libhashcat now runs in a background thread. I ran into some interesting issue while testing. Mainly, the if the interpreter exits before hashcat is finished then we'll get a segfault. I think when events are implemented this will be avoided.
When libhashcat is executing the Python interpreter is locked up until the function returns. We need a solution for this issue. One option is to start a new thread in the extension code, and the other is to try and use Python's builtin threading library to call the function. Either way I think we'll need to make sure we're not allowing users to corrupt shared memory.
I'm open to any design suggestions.