Skip to content
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

When debugging make variables output optional #2928

Closed
Mzack9999 opened this issue Nov 30, 2022 · 2 comments
Closed

When debugging make variables output optional #2928

Mzack9999 opened this issue Nov 30, 2022 · 2 comments
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@Mzack9999
Copy link
Member

Nuclei version:

main and dev

Current Behavior:

The -debug flag prints out request/response + variables, making the output unreadable

Expected Behavior:

Variables should be printed in a more concise way (eg. batched inline) or only if requested

Steps To Reproduce:

$ go run . -t test.yaml -debug -u http://scanme.sh
...
[DBG] Protocol response variables:
        1. Scheme => https
        2. service => sts
        3. BaseURL => http://scanme.sh
....
        100. File => /
...
@Mzack9999 Mzack9999 added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Nov 30, 2022
@ehsandeep
Copy link
Member

@Mzack9999 this is already done in dev, as part of #2670

@Mzack9999
Copy link
Member Author

Duplicate of #2670

@Mzack9999 Mzack9999 marked this as a duplicate of #2670 Nov 30, 2022
@Mzack9999 Mzack9999 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

2 participants