trufflehog 3.29.1 releases: Searches through git repositories for secrets, digging deep into commit history and branches

Truffle Hog

Searches through git repositories for secrets, digging deep into commit history and branches. This is effective at finding secrets accidentally committed.

NEW

Trufflehog previously functioned by running entropy checks on git diffs. This functionality still exists, but high signal regex checks have been added, and the ability to suppress entropy checking has also been added.

These features help cut down on noise and makes the tool easier to shove into a devops pipeline.

truffleHog –regex –entropy=False https://github.com/dxa4481/truffleHog.git

or

truffleHog file:///user/dxa4481/codeprojects/truffleHog/

How it works

This module will go through the entire commit history of each branch, check each diff from each commit, and check for secrets. This is both by regex and by entropy. For entropy checks, trufflehog will evaluate the Shannon entropy for both the base64 charset and hexadecimal charset for every blob of text greater than 20 characters comprised of those character sets in each diff. If at any point a high entropy string >20 characters is detected, it will print to the screen.

Changelog v3.29.1

• Make slack webhook detector regex more specific by @trufflesteeeve in #1168

Install

pip install truffleHog

Usage

Find secrets hidden in the depths of git.



positional arguments:

  git_url               URL for secret searching



optional arguments:

  -h, --help            show this help message and exit

  --json                Output in JSON

  --regex               Enable high signal regex checks

  --entropy DO_ENTROPY  Enable entropy checks

  --since_commit SINCE_COMMIT

                        Only scan from a given commit hash

  --max_depth MAX_DEPTH

                        The max commit depth to go back when searching for

                        secrets

Customizing

Custom regexes can be added to the following file:

truffleHog/truffleHog/regexChecks.py

Things like subdomain enumeration, s3 bucket detection, and other useful regexes highly custom to the situation can be added.

Feel free to also contribute high signal regexes upstream that you think will benefit the community. Things like Azure keys, Twilio keys, Google Compute keys, are welcome, provided a high signal regex can be constructed.

Copyright (C) 2017 dxa4481 

Source: https://github.com/dxa4481/