News for hackers. Stuff that matters.
Re:Show HN: GitMonKey – monitor your repos and commits for e... by rgun on Thursday April 20, 2017 @12:06PM (#14157918)
* 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?
Re:Show HN: GitMonKey – monitor your repos and commits for e... by shaharsol on Thursday April 20, 2017 @01:27PM (#14158800)
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
Re:Show HN: GitMonKey – monitor your repos and commits for e... by ohyeshedid on Thursday April 20, 2017 @02:01PM (#14159155)
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

Re:Show HN: GitMonKey – monitor your repos and commits for e... by newman314 on Thursday April 20, 2017 @02:18PM (#14159291)
Is there a tool that can do this check as a pre-commit hook?