The devs shouldn’t have access to prod credentials in the first place. That’s the real issue.
Re:Beej's Guide to Git
by sampullman on Wednesday February 05, 2025 @12:18AM
(#42944141)
Commiting credentials is also a real issue, best to avoid doing both.
Internal audit said the same thing.
Quelle surprise!
Re:Beej's Guide to Git
by zelphirkalt on Wednesday February 05, 2025 @07:44AM
(#42947717)
Then you need to hire someone else to manage the deployment of services though.
Sounds like you need a pre-commit hook to check.
Pre commit hooks aren’t enforcable. People need to opt in to them, and the people who opt in to them are the people who will check for passwords before they commit.
Re:Beej's Guide to Git
by n_plus_1_acc on Wednesday February 05, 2025 @05:43AM
(#42946680)
Server-side pre-recieve hooks are better
Because the C and PL/SQL people are on CVS, I can fix this with vi on the ,v archive.
First on TFS repositories, and now with git grep I can easily find exposed passwords for many things. But it's just SQL Server!
We will never be able to use git responsibly, so I will peruse this guide with academic interest.
Don't even get me started on secrecy management.
I am looking forward to retirement!