Open 0xhunster opened 2 years ago
It did work, didn't it?
...
[10:12:52] Starting: wp-admin/
[10:13:23] Starting: wp-admin/css/
[10:13:56] Starting: wp-admin/images/
[10:14:29] Starting: wp-admin/includes/
[10:15:00] Starting: wp-admin/js/
[10:15:31] Starting: wp-admin/maint/
...
yes, work. But it should be scanned only 2. but not work.
[10:12:52] Starting: wp-admin/
[10:13:23] Starting: wp-admin/css/
Hi @0xhunster, I think you misunderstood the feature, "max recursion depth" is the maximum path depth to perform recursion. For example, if dirsearch finds /api/v2/
, the path depth is 2 (/api
and /v2
), so if you set the maximum recursion depth to 1, it won't brute-force it.
oh, ok thanks for clearing this. Any way to scan only 2 recursive then stop. I mean, Added to the queue:
jobs work only two times.
[10:12:52] Starting: wp-admin/
[10:13:23] Starting: wp-admin/css/
Well, maybe I will add that feature, but I need to know the purpose/usage of this feature first. What are the use cases, who will use it?
It's very important because nowadays we are doing a lot of automation. so, when we will do automation with dirsearch with recursion function, then dirseach will work with recursion, but when dirsearch found a directory then added to the queue, but if directory found more than 20. Then it will very time to get the result. So, If we set the jobs queue, it will be got the result in less time. I hope you understand.
@0xhunster I think when a hacker scans a target, they must expect to find all the possible paths, missing any path can lead to missing a vulnerability. dirsearch allows you to save the progress and continue later, so no need to ignore the results just for time complexity
when I set --max-recursion-depth 1 or -R 1 it works fine :)
but when I set --max-recursion-depth 2 or -R 2 didn't works it anymore.