this post was submitted on 22 Sep 2023
19 points (95.2% liked)
appsec
331 readers
1 users here now
A community for all things related to application security.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You shouldn't be hard-coding API keys, and definitely not committing them to the repository.
For local development you would definitely keep them in a config file. Nothing wrong with that.
For production they are set during the release process.
Nothing is more expensive than developers needing to find all the configs and keys to just start up a project to make a small fix somewhere.
A config file outside of the repository to be specific.
On Linux it can go somewhere under ~
On windows it can go somewhere in AppData
Ie;
~/YourAppName/Secrets.jsonor whatever your config file flavor is. Json, yaml, xml, whatevsNo. For development purposes I want my devs to be able to clone the repo and start.
So the development config files are inside the repositories.
Wow, that's a terrible security process even for development configs. How about adding a script they can run right after cloning to pull the needed keys from a secure location using their own user credentials? Plenty of solutions out there.
So let’s say the code base leaks.
Let’s say our VPN was also compromised.
Then what is the worst that can happen? Some internal dev api with no real data in it can be tested by hackers.