Read-only filesystem fixes for when ~/.config is not writable #3990
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.
Proposed changes
When running nuclei in a lambda function, I ran into the issues described in #3576.
I've been using the changes locally for a few months with great success, but I understand that this might break existing installs so I am not sure if this is something that will even be considered.
I know there is a bit of testing and etc to sort out, but as I have not done any nuclei PRs out side of the templates project, I figured the best course of action was just to start a PR and get a dialog going.
Checklist