sops icon indicating copy to clipboard operation
sops copied to clipboard

Simple and flexible tool for managing secrets

Results 280 sops issues
Sort by recently updated
recently updated
newest added

First-party Kubernetes support would be a wonderful addition to sops, the ability to read from and write to secrets manifests. It shouldn't be too dissimilar to the YAML or JSON...

Sops uses AES-GCM that is an authentication encryption mode, providing both confidentiality and integrity/authenticity of the encrypted configuration values. That is, nobody can read them and also nobody can alter...

Using it on Linux based os, want to try it on windows (local), didn't succeed so far. Please share doc for the same.

Hi folks. My approach to allowing users to create secrets, and then for CI to decrypt and use those secrets, is to allow users to create encrypted files using the...

I'm unable to build this project with a recent version of protobuf and it seems like this hasn't been updated in a while. In an effort to try make it...

This reduces the sops configuration stored in files to its bare minimum: ```yaml # example with GCP KMS someConfig: ... sops: gcp_kms: - resource_id: projects/some-project/locations/global/keyRings/some-keyring/cryptoKeys/some-key created_at: "2024-08-31T01:09:49Z" enc: someenc= lastmodified:...

Our scanning jobs have identified a new CVE "[CVE-2024-24791](https://www.cve.org/CVERecord?id=CVE-2024-24791)" in the sops binary v3.9.0. This is an issue with the Go standard library net/http. Is it possible to rebuilt sops...

| failed to decrypt sops data key with GCP KMS key: context | deadline exceeded I did login GCP and still cannot make it work It always timeout with vpn...

using sops 3.8.1 My `.sops.yaml` I am able to encrypt and decrypt SOPS secrets using this configuration: ``` creation_rules: - path_regex: \.yaml$ key_groups: - kms: - arn: 'arn:' role: 'arn:'...

I've upgraded our sops binary from v3.8.1 to v3.9.0. Without changing any encrypted file, our pipeline jobs started failing due to this new error. I've put together a few steps...

bug
keyservice/awskms