-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Max sub-directories for recursion #1091
Comments
It did work, didn't it?
|
yes, work. But it should be scanned only 2. but not work.
|
Hi @0xhunster, I think you misunderstood the feature, "max recursion depth" is the maximum path depth to perform recursion. For example, if dirsearch finds |
oh, ok thanks for clearing this. Any way to scan only 2 recursive then stop. I mean,
|
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.
The text was updated successfully, but these errors were encountered: