You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you so much for this great tool! I use it at least once a week on pentests.
As part of my internal pentest workflow, I will perform directory enumeration against the whole internal network. However, to do this right now I have to run a tool to figure out which ports support HTTP(S) and then parse that tool output and send it as input to ffuf. It would be very helpful to have an option that would ingest a straight Nmap XML file, attempt HTTP and HTTPS connections to each port to see what port/host combo's support HTTP(S), and then kickoff a directory enumeration scan with ffuf.
Yeah, doing this outside of ffuf is preferred. The general design philosophy is "if you can do it outside of ffuf, you should".
This is in place in order to not to bloat the codebase into a unmaintainable behemoth, trying to support every and all use cases, I hope you understand :)
Thank you so much for this great tool! I use it at least once a week on pentests.
As part of my internal pentest workflow, I will perform directory enumeration against the whole internal network. However, to do this right now I have to run a tool to figure out which ports support HTTP(S) and then parse that tool output and send it as input to ffuf. It would be very helpful to have an option that would ingest a straight Nmap XML file, attempt HTTP and HTTPS connections to each port to see what port/host combo's support HTTP(S), and then kickoff a directory enumeration scan with ffuf.
Something like the following:
The text was updated successfully, but these errors were encountered: