GitLeaks – Search engine for exposed secrets on GitHub

Re:GitLeaks – Search engine for exposed secrets on GitHub by sarreph on Friday February 17, 2017 @07:02AM (#13667619)

What a shame that you had to expose everyone's mistakes like this in such a blanket fashion.

You could've taken the moral high ground and created a reverse-search such as HaveIBeenPwned[0], whereby you check repos you own.

I hope this gets taken down because the potential for abuse is ripe.

[ Parent | on HN ]

Re:GitLeaks – Search engine for exposed secrets on GitHub by lrusnac on Friday February 17, 2017 @07:06AM (#13667646)

that's such a great idea, although I think people that would sign up for this service would know not commit credentials

[ Parent | on HN ]

Re:GitLeaks – Search engine for exposed secrets on GitHub by Xylakant on Friday February 17, 2017 @07:10AM (#13667673)

We all make mistakes despite better knowledge. I'd probably sign up.

[ Parent | on HN ]

Re:GitLeaks – Search engine for exposed secrets on GitHub by lrusnac on Friday February 17, 2017 @07:16AM (#13667704)

sure, but it's more likely for somebody that doesn't know about this service to publish a secret than someone that is aware of it

[ Parent | on HN ]

Re:GitLeaks – Search engine for exposed secrets on GitHub by the_duke on Friday February 17, 2017 @07:08AM (#13667655)

Well, the service could auto-create an issues for each repository that contains secrets.

[ Parent | on HN ]

Re:GitLeaks – Search engine for exposed secrets on GitHub by lrusnac on Friday February 17, 2017 @07:15AM (#13667700)

well, that's kinda the same, facilitating finding the secrets since it's easy to search for issues, feel like a private notification is way better

[ Parent | on HN ]