-
Notifications
You must be signed in to change notification settings - Fork 47
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
docs: add encrypting secrets spec #113
docs: add encrypting secrets spec #113
Conversation
Signed-off-by: Dwi Siswanto <[email protected]>
|
||
We are prioritizng support for: | ||
<Note> | ||
This feature is available in Nuclei **vX.Y.Z**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TBD. @ehsandeep
- **AWS Secrets Manager** | ||
#### Recommended SOPS Configuration | ||
|
||
To simplify the encryption process, you can set up a [`.sops.yaml`](https://github.com/projectdiscovery/nuclei/blob/dev/.sops.yaml) file with rules that automatically encrypt specific [fields](/tools/nuclei/authenticated-scans#secret-file-fields) in your files. Here's a recommended configuration: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: update dev
with main
when this gets merged into main branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't have to wait tho
merging this, let me know if you want me to hold this PR or revert this. |
Superseded by #129 |
Satisfy projectdiscovery/nuclei#5841