Live data from Hacker News

Show HN: GitMonKey – monitor your repos and commits for exposed private keys

gitmonkey.io

41–50 of 50 posts

Re: Show HN: GitMonKey – monitor your repos and commits for exposed private keys

#41
post #39

* 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?

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 exposed private keys

#42
post #40

http://pre-commit.com/hooks.html calling attention to detect-private-key and detect-aws-credentials (disclaimer-ish: was original contributor on the latter hook but been way expanded since then) edit: obviously each dev needs to have this set up, not a catch-all third party tool.

Have an example hook I can test out? Thanks!

Re: Show HN: GitMonKey – monitor your repos and commits for exposed private keys

#43
post #39

* 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?

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

Re: Show HN: GitMonKey – monitor your repos and commits for exposed private keys

#46
post #3

Earlier quoted context omitted.

Agreed. Or software you can just run internally. Not a fan of just opening up read access to my code to a new startup.

There are git hooks that u can run locally, but think as a manager of an R&D team of 10-20 developers. You need to make it centralised.

No, if I want to do my job correctly I'll encourage best practices and address careless deviations. I won't encourage bad behaviour by outsourcing simple workflow tooling to a third party that doesn't have any accountability if they drop the ball.

Whether you realize it or not, you're advocating for increasing surface area and risk. You're offering a service to people with bad opsec while simultaneously asking them to trust your opsec; none of which is a good solution to the actual problem.

Re: Show HN: GitMonKey – monitor your repos and commits for exposed private keys

#47
post #40

http://pre-commit.com/hooks.html calling attention to detect-private-key and detect-aws-credentials (disclaimer-ish: was original contributor on the latter hook but been way expanded since then) edit: obviously each dev needs to have this set up, not a catch-all third party tool.

Have an example hook I can test out? Thanks!

what do you mean? like one i recommend for a simple test? or a sample config?

Re: Show HN: GitMonKey – monitor your repos and commits for exposed private keys

#48
post #23

Why should I trust you guys? I also recognize standard templates from miles away. EDIT: found the template http://demo.templateocean.com/premium/template/landx/layout-...

Hilarious. No customization at all!

https://news.ycombinator.com/showhn.html

Re: Show HN: GitMonKey – monitor your repos and commits for exposed private keys

#50
post #7

How about this one? https://github.com/dxa4481/truffleHog Posted here a few months ago.

Also, if you want to have more control over what gets matched (as opposed to only checking entropy): https://github.com/ezekg/git-hound (I'm the author of this one.)
Post reply on HN