News for hackers. Stuff that matters.

A comment on How a bug in VS2015 exposed my source code on GitHub and cost me $6,500. Parent comment

Re:How a bug in VS2015 exposed my source code on GitHub and ... by nailer on Monday August 31, 2015 @06:26PM (#10149496)
> Encrypt access keys in config files instead of just leaving them exposed in the config file.

How do decrypt them when you app re-launches? How do you decrypt them automatically on every instance?

[ Parent | on HN ]
Re:How a bug in VS2015 exposed my source code on GitHub and ... by voltagex_ on Monday August 31, 2015 @07:15PM (#10149711)
I've moved to using environment variables. I realise they have their own security challenges but at least I'm not accidentally going to git push the keys.
[ Parent | on HN ]
Re:How a bug in VS2015 exposed my source code on GitHub and ... by wereHamster on Monday August 31, 2015 @11:47PM (#10150615)
But you probably want to store the descriptions of the instances and what runs on them in a git repository. It doesn't matter whether you use env variables or something else. At some point you will have a git repository which stores the CM for your whole infrastructure.
[ Parent | on HN ]