This was a pain to track down, and I'm sorry I don't have the time at the moment to submit a proper PR.

For anyone experiencing this issue:
This appears to be happening because the reeper class is not terminating properly, OR because it is throwing some exception that isn't properly handled and the still open Python bug (http://bugs.python.org/issue9400) is hanging the process.

Workaround/Fix:

The final messages printed, mentioned by @aboul3la above, happen at the end of the run method around lines 724-731 of subbrute.py. If you force reeper to terminate, the process will exit properly. That means adding the following code: reep.terminate() at line 727 of subbrute.py (reep is an instance of reeper in this context):

    #We no longer require name servers.
    try:
        killproc(pid = verify_nameservers_proc.pid)
        reep.terminate() #**ADDED THIS LINE HERE, EXITS PROPERLY**
    except:
        #Windows threading.tread
        verify_nameservers_proc.end()
    trace("End")

If some kind soul could submit a proper pull request, or the tool author could do a quick update to master that would be great. Otherwise I will try to get something out in the next week so this is handled.

Cheers

from subbrute.

Great job @binarycanary. Thanks a lot for your help!

from subbrute.

PR submitted for permanent fix: #48

from subbrute.

Due to this problem I have removed reeper entirely. DNSLIb was still hanging on broken sockets. I have updated DNSlib and more testing is needed.

Thanks for your help!

from subbrute.

Oh cool! I was wondering if you might consider committing your development branch to github that has the dnslib updates and reeper removed?

At the moment, you can't integrate subbrute into any larger scripted solution because it never returns. I'm currently set up to use my own fork, so I can integrate with automation, but it would be nice to be using the official resource.

from subbrute.