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

Add commit hash to the ouput #16

Open
tosiara opened this issue Jan 6, 2020 · 0 comments
Open

Add commit hash to the ouput #16

tosiara opened this issue Jan 6, 2020 · 0 comments

Comments

@tosiara
Copy link

tosiara commented Jan 6, 2020

Currently there is no way to know which revision has caused the leak.
For example:

--------------------------------------------------------------------------------
                     gittyleaks' Bot Detective at work ...                      
--------------------------------------------------------------------------------
file: 2.c
what: user
value: admin;
match:
    user=admin;
num_of_revisions: 1
----------------------------------------
file: 3.c
what: user
value: admin;
match:
    user=admin;
num_of_revisions: 1
----------------------------------------
file: 3.c
what: password
value: 1234;
match:
    password=1234;
num_of_revisions: 1
----------------------------------------
file: 2.c
what: password
value: 1234;
match:
    password=1234;
num_of_revisions: 1
----------------------------------------

$ ls
3.c

As you can see, the file 2.c has been reported, but it is no longer in the tree. If there was git commit's SHA1 in the output - it would be easier to track when and who leaked the secret

Thanks

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

No branches or pull requests

1 participant