News for hackers. Stuff that matters.
Re:Show HN: GitMonKey – monitor your repos and commits for e... by dberg on Thursday April 20, 2017 @08:35AM (#14156058)
Agreed. Or software you can just run internally. Not a fan of just opening up read access to my code to a new startup.
Re:Show HN: GitMonKey – monitor your repos and commits for e... by fredley on Thursday April 20, 2017 @08:38AM (#14156077)
Yeah, what if gitmonkey accidentally reveal a secret key? Now somebody has a curated list of everyone's git's secret keys - even the ones in private repos!
Re:Show HN: GitMonKey – monitor your repos and commits for e... by shaharsol on Thursday April 20, 2017 @08:51AM (#14156172)
If GitMonkey has your key on record - it means we're not the only ones having it. You should revoke it immediately. So even if our db is breached, it should only contain a list of useless revoked keys.
Re:Show HN: GitMonKey – monitor your repos and commits for e... by fredley on Thursday April 20, 2017 @08:58AM (#14156222)
> should
Re:Show HN: GitMonKey – monitor your repos and commits for e... by MightySCollins on Thursday April 20, 2017 @09:30AM (#14156411)
I am also really scared by the suggestion that they might 'take a leap' and check if it's valid... Then they have a list of keys and whether they work or not
Re:Show HN: GitMonKey – monitor your repos and commits for e... by CGamesPlay on Thursday April 20, 2017 @11:17AM (#14157429)
If you signed up for a service specifically to detect when you compromise your secrets, and the service tells you about it, and you don't change the secret... Why are you then worried that the other party gets compromised?
Re:Show HN: GitMonKey – monitor your repos and commits for e... by shaharsol on Thursday April 20, 2017 @08:38AM (#14156074)
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.
Re:Show HN: GitMonKey – monitor your repos and commits for e... by ohyeshedid on Thursday April 20, 2017 @02:49PM (#14159617)
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.