Releases: DevSecOpsDocs/nuclearpond
Releases · DevSecOpsDocs/nuclearpond
v0.2.2
No changes in the client but since so many infrastructure improvements were made, creating a new release.
- Nuclei failures, exit code status 1, will still output cmd output for debugging
- Massively improved private nuclei templates through github terraform provider on release tags
- Added full support for nuclei configuration files
Infrastructure Pull Request: https://github.com/DevSecOpsDocs/terraform-nuclear-pond/pull/2/files
Note: Please destroy and recreate your infrastructure to avoid issues
v0.2.1
Whats new?
Write json output to results.json, cleanup code, and fix duplicate logs.
v0.2
Whats new?
Improved infrastructure and added support for NuclearPond server that allows you to execute scans through an API.
- Requires API key for performing scans and retrieving state
- Stores state of scans in dynamodb
- Logs scans as they are performed
Infrastructure Changes
The majority of changes is in the backend infrastructure that allows for:
- Support for custom nuclei templates
- DynamoDB to store scan states when using nuclearpond http server
- Added outputs to easily reference resources
- Code cleanup for Nuclei runner
- Improved terraform module variables to avoid confusion
Initial release of nuclear pond!
Completed debugging of working proof of concept. Please feel free to submit issues!