Description:
When working with Wfuzz, I noticed that the output provides valuable information about the fuzzing process. However, I believe that adding a few more columns to the output can provide a more comprehensive analysis of the results.
Current Columns:
ID
Response
Lines
Word
Chars
Request
Proposed Additional Columns:
Method
URL
Reason
RTT
Size Req. Header
Size Req. Body
Size Resp. Header
Size Resp. Body
State
Payloads
Benefits:
Detailed insights into the behavior and efficiency of the fuzzing attempts.
Better understanding of response dynamics like Round-Trip Time (RTT) and response sizes.
Enhanced context from fields like Message Type, Method, and URL.
Improved debugging with more granular data.
Contribution:
I am enthusiastic about contributing to this enhancement. Although I'm new to open-source contributions and still building my programming skills, I'm willing to help develop these columns. However, as a beginner, I would appreciate guidance to ensure I align with the project's standards and practices.
Description: When working with Wfuzz, I noticed that the output provides valuable information about the fuzzing process. However, I believe that adding a few more columns to the output can provide a more comprehensive analysis of the results.
Current Columns:
Proposed Additional Columns:
Benefits:
Contribution: I am enthusiastic about contributing to this enhancement. Although I'm new to open-source contributions and still building my programming skills, I'm willing to help develop these columns. However, as a beginner, I would appreciate guidance to ensure I align with the project's standards and practices.
Cheers, Volkan