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

Scan sometimes displays wrong line number #1031

Closed
RebeckaForsberg opened this issue Jan 18, 2023 · 2 comments
Closed

Scan sometimes displays wrong line number #1031

RebeckaForsberg opened this issue Jan 18, 2023 · 2 comments
Labels

Comments

@RebeckaForsberg
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

TruffleHog Version

3.25.2

Expected Behavior

When running the Trufflehog the output containing the line number should match the line in the actual commit.

Actual Behavior

The lines do sometimes not match.

Steps to Reproduce

We are running Trufflehog on internal repositories with the command:
trufflehog git --only-verified

and the output in the terminal shows a line number. When searching for the commit in Azure DevOps the secret sometimes appears on a different line than stated in the output.

Environment

  • OS: macOS Monterey
  • Version 12.6

Additional Context

When the lines do not match, the line number in the commit is around five lines below or above.

@dustin-decker
Copy link
Contributor

Could you provide the secret type that you observed this issue with?

@zricethezav
Copy link
Collaborator

@RebeckaForsberg if this is still an issue feel free to reopen. If you do can you provide more details and a way for us to reproduce this bug? Thanks!

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

No branches or pull requests

3 participants