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

Add {datetime} variable for output filename/URL #1448

Open
strongestplayer1 opened this issue Jan 6, 2025 · 8 comments · May be fixed by #1451
Open

Add {datetime} variable for output filename/URL #1448

strongestplayer1 opened this issue Jan 6, 2025 · 8 comments · May be fixed by #1451
Labels
enhancement New feature or request Priority: Low

Comments

@strongestplayer1
Copy link

I have a question about the output-file option in the config.ini file?

I tested it and it creates many url files in the reports directory. Is it possible to not create so many files, and instead create just one like in the previous version?
1

@strongestplayer1 strongestplayer1 added the question Further information is requested label Jan 6, 2025
@shelld3v
Copy link
Collaborator

shelld3v commented Jan 8, 2025

Yes, just remove those variables so every scan will have the same output file, and that file will have the report of all scans from all targets

@shelld3v shelld3v closed this as completed Jan 8, 2025
@strongestplayer1
Copy link
Author

Yes, just remove those variables so every scan will have the same output file, and that file will have the report of all scans from all targets

That's not right
I modified it like this, but the reports folder was not created and no results were saved

image

@strongestplayer1
Copy link
Author

The result is a reports file, not a reports folder

@shelld3v
Copy link
Collaborator

Maybe reports/output.txt instead of reports/ would work?

@shelld3v shelld3v reopened this Jan 12, 2025
@strongestplayer1
Copy link
Author

Maybe reports/output.txt instead of reports/ would work?也许 reports/output.txt 而不是 reports/ 会奏效?

You're right, but it doesn't feel as useful as before. Previously, it directly generated folder results for specific times
image

@strongestplayer1
Copy link
Author

At present, only the following content can be used:
Output file=report/{date}. {Extension}
To generate the result for the current date.

These results will include all tests conducted on that day.

Is there any other way to generate time results similar to the old version using the new version, besides using the old version?

@shelld3v
Copy link
Collaborator

So reports/${date}/${host}_${port}.${extension} isn't what you want because you run dirsearch several times a day and you want a new folder each time? Probably the solution right now is to locate your output manually using --output-file. I might consider adding something like ${datetime} to solve this problem in case there are enough people out there who need this

@strongestplayer1
Copy link
Author

So reports/${date}/${host}_${port}.${extension} isn't what you want because you run dirsearch several times a day and you want a new folder each time? Probably the solution right now is to locate your output manually using --output-file. I might consider adding something like ${datetime} to solve this problem in case there are enough people out there who need this那么 reports/${date}/${host}_${port}.${extension} ,你每天运行 dirsearch 几次并且每次都想要一个新文件夹,这难道不是你想要的吗?现在的解决方案可能是使用 --output-file 手动查找您的输出。我可能会考虑添加类似 ${datetime} 的东西来解决这个问题,以防有足够多的人需要这个

Okay, thank you

@shelld3v shelld3v added enhancement New feature or request Priority: Low and removed question Further information is requested labels Jan 23, 2025
@shelld3v shelld3v changed the title I have a question about the output-file option in the config.ini file Add {datetime} variable for output filename/URL Jan 23, 2025
@shelld3v shelld3v linked a pull request Jan 23, 2025 that will close this issue
@shelld3v shelld3v linked a pull request Jan 23, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Priority: Low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants