N7x@infosec.pub to appsec@infosec.pubEnglish · 1 year agoGitHub Copilot, Amazon Code Whisperer emit people's API keyswww.theregister.comexternal-linkmessage-square11fedilinkarrow-up120
arrow-up120external-linkGitHub Copilot, Amazon Code Whisperer emit people's API keyswww.theregister.comN7x@infosec.pub to appsec@infosec.pubEnglish · 1 year agomessage-square11fedilink
minus-squaretmRgwnM9b87eJUPq@lemmy.worldlinkfedilinkEnglisharrow-up1·1 year agoNo. 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.
minus-squareDoomBot5@lemmy.worldlinkfedilinkEnglisharrow-up1·1 year agoWow, 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.
minus-squaretmRgwnM9b87eJUPq@lemmy.worldlinkfedilinkEnglisharrow-up1·1 year agoSo 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.
No. 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.