Wow this thread made me realize there are so many tools for this.
Just to throw in another one, at my company we are using git-crypt [1], and it works pretty well in our case
Simple and flexible tool for managing secrets
31–34 of 34 posts
Re: Simple and flexible tool for managing secrets
#32We developed an open standard for storing encrypted secrets alongside code in your git/whatever repo: https://neosmart.net/blog/2020/securestore-open-secrets-form...
The format is language/platform agnostic and we’ve releases libraries for .NET/C# and rust, as well as developed two separate CLI utilities that can create and manage the stores.
Re: Simple and flexible tool for managing secrets
#33Wow this thread made me realize there are so many tools for this. Just to throw in another one, at my company we are using git-crypt [1], and it works pretty well in our case [1] https://github.com/AGWA/git-crypt
My experience with git-crypt is it works fine until you have a merge conflict. This tool seems a lot more compelling in that regard, since only encrypting the subset of the file that needs to be secret I'd imagine diffs and merge conflict would be pretty seamless.
Re: Simple and flexible tool for managing secrets
#34Even better, IMO, would be if all targets were also proxies and a client could choose -- at "query time" -- any combination of (proxy, target) that they prefer. If you wanted to go a step further, you can even allow "chaining" of proxies, such that the path a query takes might be, in an extreme example, similar to how Tor operates: Client -> Proxy 1 -> Proxy 2 -> Proxy 3 -> Target -> Resolver -- Anyways, this is kind…
Did you comment on the wrong post? This seems unrelated to sops.
Thanks, I sure did.
I've copied it to the "Cloudflare and Apple design a new privacy-friendly internet protocol" [0] thread that it was intended for, but it's too late to delete it from this one.
--