News for hackers. Stuff that matters.
Re:Characterizing secret leakage in public GitHub repositories by novaleaf on Tuesday April 09, 2019 @10:48AM (#19615208)
This highlights the difficulty of sharing secrets with your production code. How can you get secrets into production in a secure way?

Cloud providers have proprietary solutions, but those don't work on other providers (or your local dev env).

Rolling your own secrets server seems like an expensive centralized disaster waiting to happen.

It seems like putting a secret into source code is one of the least risky options. Just make sure it's not in a public git repo.

There are no comments on this comment yet.