Hacker News new | ask | show | jobs
by rgun 3349 days ago
* Why a separate service and not a pre-commit hook? * If a third-party has seen the key, hasn't the damage already been done?
2 comments

Because it's harder to enforce on a team whereas a central service (also as a 2nd security layer) deals with it on behalf of the team/org
It often takes more thought and effort to do things properly. This seems like another service that treats the symptoms of a problem rather than the problem itself. That kind of solution encourages careless behaviour, because someone will come behind me and clean it up. Encouraging best practices is a better investment.

>(also as a 2nd security layer)

Except when it's not.[1] That means it gives careless folks a false sense of security, which I think conveys more risk than no security at all.

[1]: https://news.ycombinator.com/item?id=14157870

Is there a tool that can do this check as a pre-commit hook?