recon doesn't return after scans are done

4elta / recon

automate the boring stuff!

GNU General Public License v3.0

8 stars 3 forks source link

recon doesn't return after scans are done #83

Open ikstream opened 9 months ago

ikstream commented 9 months ago

When all scans are finished, recon doesn't always finish an seems to be stuck at the same tests to the user. recon-not-finishing

The screenshot was taken long after all scans have been finished. I can't reproduce it in any reliable way, but I observed that behaviour sometimes, when a scan was killed by the recon scan timeout.

It's not an urgent, nor a big issue, just wanted to let you know.

4elta commented 9 months ago

thank you very much for reporting this issue along with your assumption of where it might stem from. i'll look into it.

4elta commented 8 months ago

i have improved the scanner log which should help with debugging this issue

ikstream commented 5 months ago

Seems like this can also happen in the middle of a scan. What I can see so far it seems related to scans killed by recon.

What I can read from it is the following:

a scan hits the timeout barrier and is killed
the other current scans finish
no new hosts are processed and the main recon thread keeps running, but has no childs anymore.