Added support for hashed directories #8
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you use CertStreamMonitor to track many websites like me, the number of JSON files created in the alerts directory may quickly become unmanageable.
I added support for hashed directories to create sub-directories based on the server current time.
You can define an alerts directory in the config like:
./alerts/%%Y/%%m/%%d
And sub-directories will be created to store alerts at each new scanhost.py execution.
What do you think about an option to create hashed directories based on the FQDN?
Ex:
./alerts/be/rootshell/blog/