Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

offline cloned repository scanning #22

Open
techgaun opened this issue Mar 3, 2017 · 2 comments
Open

offline cloned repository scanning #22

techgaun opened this issue Mar 3, 2017 · 2 comments

Comments

@techgaun
Copy link
Owner

techgaun commented Mar 3, 2017

the way it would work is run github-dorks as an offline tool and use regex and text patterns to find potential leaks.. optionally see if we can also scan history

@Plazmaz
Copy link
Collaborator

Plazmaz commented Mar 3, 2017

I like the idea of setting up a pre-commit hook.

@Plazmaz
Copy link
Collaborator

Plazmaz commented Jul 20, 2017

Actionable steps to achieve this:

  1. Clone repo. I suggest using GitPython or similar for git management.
  2. Write system for parsing GitHub search syntax, similar to https://github.com/Plazmaz/GHScraper/blob/master/index.js#L16-L33 and https://github.com/Plazmaz/GHScraper/blob/master/index.js#L89-L113 (sorry, messy)
  3. Convert dorks into objects
  4. Iterate commit diffs via GitPython and check them against the objects

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants