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

Markdown results in separate directories. #3596

Closed
cpandya2909 opened this issue Apr 24, 2023 · 5 comments · Fixed by #3961
Closed

Markdown results in separate directories. #3596

cpandya2909 opened this issue Apr 24, 2023 · 5 comments · Fixed by #3961
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@cpandya2909
Copy link

Please describe your feature request:

If we output reports to Markdown with "-me" options, it creates all files in a single folder and have to search a big list for specific template output .

It would be better if we allow user to give option to save outputs in different folders.
User can choose to save outputs either hostname wise or template wise

Describe the use case of this feature:

clear identification of outputs and issues.

@cpandya2909 cpandya2909 added the Type: Enhancement Most issues will probably ask for additions or changes. label Apr 24, 2023
@kchason
Copy link
Contributor

kchason commented Jul 19, 2023

What would be the intended method for determining which categorization occurs? An environment variable such as MARKDOWN_EXPORT_SORT_MODE that defaults to as it currently stands, but optionally allows "host" and "template"?

@cpandya2909
Copy link
Author

yes, that can work, or else we can create 1 additional flag to mark that markdowns are stored in directory.

@kchason
Copy link
Contributor

kchason commented Jul 19, 2023

Okay, I can work on this one

@cpandya2909
Copy link
Author

Thank you

@kchason kchason mentioned this issue Jul 19, 2023
4 tasks
@tarunKoyalwar tarunKoyalwar linked a pull request Jul 20, 2023 that will close this issue
4 tasks
@ehsandeep ehsandeep added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Jul 21, 2023
@ehsandeep ehsandeep added this to the nuclei v2.9.10 milestone Jul 22, 2023
@ehsandeep
Copy link
Member

@cpandya2909 this is now possible with latest release - https://github.com/projectdiscovery/nuclei/releases/tag/v2.9.10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants