Live data from Hacker News

Simple and flexible tool for managing secrets

github.com

11–20 of 34 posts

Re: Simple and flexible tool for managing secrets

#11
Neat! I like that it maintains everything in the same file. No need to mess with .gitignore

Have you tried BlackBox?

Projects like https://github.com/StackExchange/blackbox have the benefit of using GPG group encryption. Each person has their own secret key but any one key can decrypt the file. This makes key rotation easier.

Re: Simple and flexible tool for managing secrets

#12

Neat! I like that it maintains everything in the same file. No need to mess with .gitignore Have you tried BlackBox? Projects like https://github.com/StackExchange/blackbox have the benefit of using GPG group encryption. Each person has their own secret key but any one key can decrypt the file. This makes key rotation easier.

Sops can use GPG key groups too. There are multiple encryption methods available, such as GPG, KMS (GCP and AWS) and azure key vault.

Re: Simple and flexible tool for managing secrets

#15

I am surprised Mozilla developers chose to write this project in Go instead of Rust, but do not get me wrong, I like Go, it is my primary programming language at work, and I always try to advocate for the right tool for the job. I still find it curious, though. I guess it was easier to translate Python to Go than to Rust.

I’m guessing it’s the deployment story that made them choose Go.

Re: Simple and flexible tool for managing secrets

#16
worked with this at a previous job - pro tip if you're doing anything with KMS (and are doing a lot of role assumption, etc), set

    AWS_SDK_LOAD_CONFIG=1
https://github.com/mozilla/sops/issues/471#issuecomment-5036... (and i'm sure countless other references)

Generally found that setting that env var with anything mildly complicated (in go!) in terms of AWS roles helps.

Other libraries/clis/etc (in other languages) tend to transparently traverse the credentials chain for you.

Re: Simple and flexible tool for managing secrets

#17
What is the purpose of encrypting just the values and not the keys? If you need to run the file through sops to decrypt the values before using it, why not just encrypt the entire file?

Is it just for easier debugging, so you can see the structure of the encrypted file?

Re: Simple and flexible tool for managing secrets

#20
post #17

What is the purpose of encrypting just the values and not the keys? If you need to run the file through sops to decrypt the values before using it, why not just encrypt the entire file? Is it just for easier debugging, so you can see the structure of the encrypted file?

For version controlling this could be useful.
Post reply on HN