News for hackers. Stuff that matters.
Re:Incident Report: Inadvertent Private Repository Disclosure by jasonmoo on Friday October 28, 2016 @03:48PM (#12819975)
I wrote the script in question and actually used a simple shannon entropy value. (http://codereview.stackexchange.com/questions/868/calculatin...). It worked well enough help rule out several problem spaces.
Re:Incident Report: Inadvertent Private Repository Disclosure by pavel_lishin on Friday October 28, 2016 @04:23PM (#12820269)
Would you mind posting the script? I'd love to run it against our codebase and see what it comes up with.

It might be a fun thing to open source as part of a "I've inherited a project, what now?" toolkit that helps you decide what to fix.

Re:Incident Report: Inadvertent Private Repository Disclosure by jasonmoo on Friday October 28, 2016 @04:43PM (#12820488)
Sure. It's a simple tool but the concept could be augmented toward something like the scenario you described.

https://gist.github.com/jasonmoo/06691c8fea09b62aa35235fc93e...

Re:Incident Report: Inadvertent Private Repository Disclosure by ubernostrum on Friday October 28, 2016 @07:32PM (#12821664)
IIRC Instagram released a plugin for Bandit (the OpenStack static analyzer for Python) that does this.