Просмотр исходного кода

Merge pull request #29 from loicbourgois/patch-1

Update README.md
Zachary Rice 8 лет назад
Родитель
Сommit
f58caef16d
1 измененных файлов с 3 добавлено и 3 удалено
  1. 3 3
      README.md

+ 3 - 3
README.md

@@ -26,7 +26,7 @@ go get -u github.com/zricethezav/gitleaks
 ./gitleaks {git url}
 ./gitleaks {git url}
 ```
 ```
 
 
-This example will clone the target `{git url}` and run a diff on all commits. A report will be output to `{repo_name}_leaks.json`
+This example will clone the target `{git url}` and run a diff on all commits. A report will be outputted to `{repo_name}_leaks.json`
 Gitleaks scans all lines of all commits and checks if there are any regular expression matches. The regexs are defined in `main.go`. For example if a line in a commit diff like `AWS_KEY='AKAI...'` exists then the value after the assignment operator will be checked for entropy. If the value is above a certain entropy threshold then we assume that the line contains a key/secret. Work largely based on  [https://people.eecs.berkeley.edu/~rohanpadhye/files/key_leaks-msr15.pdf](https://people.eecs.berkeley.edu/~rohanpadhye/files/key_leaks-msr15.pdf) and https://github.com/dxa4481/truffleHog.
 Gitleaks scans all lines of all commits and checks if there are any regular expression matches. The regexs are defined in `main.go`. For example if a line in a commit diff like `AWS_KEY='AKAI...'` exists then the value after the assignment operator will be checked for entropy. If the value is above a certain entropy threshold then we assume that the line contains a key/secret. Work largely based on  [https://people.eecs.berkeley.edu/~rohanpadhye/files/key_leaks-msr15.pdf](https://people.eecs.berkeley.edu/~rohanpadhye/files/key_leaks-msr15.pdf) and https://github.com/dxa4481/truffleHog.
 
 
 ##### gitLeaks User
 ##### gitLeaks User
@@ -53,11 +53,11 @@ Options:
 	-x 			Hex entropy cutoff, default is 40
 	-x 			Hex entropy cutoff, default is 40
 	-h --help 		Display this message
 	-h --help 		Display this message
 ```
 ```
-NOTE: your mileage may vary so if you aren't getting the results you expected try tweaking the entropy cutoffs and stopwords. Entropy cutoff for base64 alphabets seemed to give good results around 70 and hex alphabets seemed to give good results around 40. Entropy is calculated using http://www.bearcave.com/misl/misl_tech/wavelets/compression/shannon.html
+NOTE: your mileage may vary so if you aren't getting the results you expected try tweaking the entropy cutoffs and stopwords. Entropy cutoff for base64 alphabets seemed to give good results around 70 and hex alphabets seemed to give good results around 40. Entropy is calculated using [Shannon entropy](http://www.bearcave.com/misl/misl_tech/wavelets/compression/shannon.html).
 
 
 
 
 ### If you find a valid leak in a repo
 ### If you find a valid leak in a repo
-Please read https://help.github.com/articles/removing-sensitive-data-from-a-repository/ to remove the sensitive information from your history
+Please read the [Github article on removing sensitive data from a repository](https://help.github.com/articles/removing-sensitive-data-from-a-repository/) to remove the sensitive information from your history.
 
 
 #### TODO
 #### TODO