-
I'm not 100% clear exactly on how sops works. But from my limited understanding the intended use was for aws vms where sops would communicate with KMS to decrypt the secrets.
Unless I am mistaken, …
-
Hello 👋
**Is your feature request related to a problem? Please describe.**
- AWS instances does not provide TPM2 virtual chip by default on their EC2 service. In this context, I'm forced to use "…
ghost updated
1 month ago
-
## SUMMARY
Provide a quick summary of your bug report.
The API and Logs have the option to mask the secrets but the execution history in the GUI is showing the secrets in plain text
### STACKST…
-
Cloud KMS quotas are easily hit when we have a lot of secrets as it does a decrypt operation per file. We need to generate an envelope key per target and use that for encrypting the secrets in that ta…
-
The Zeto tokens with encryption presents a unique challenge to a client implementation that may host many babyjubjub keys.
The encryption feature in Zeto is designed as follows:
- transaction inputs …
-
Some users want their developers to be pre-authenticated with external providers (e.g. Artifactory) when they first create their workspace.
This may be to pull data in the startup script or avoid m…
-
I've run into issues like #1851 in the past and didn't realise it was due to the `SECRET_KEY` changing when recreating a config. It would be nice if we could somehow add some mitigations to this.
#…
-
The goal of this new functionality would be to encrypt secrets pushed to parameter store as SecureString type with a specified Customer Managed KMS Key.
This feature will add security to the parame…
-
When you use the general 2.x task it outputs the entire contents of the kubeconfig file to the build log/output in VSTS. We should not have this for security reasons.
dtzar updated
7 years ago
-
Add a one-time key that is used to encrypt the content and appended to the retrieval link.