Jelajahi Sumber

Update README.md

Zachary Rice 3 tahun lalu
induk
melakukan
acce01f233
1 mengubah file dengan 11 tambahan dan 19 penghapusan
  1. 11 19
      README.md

+ 11 - 19
README.md

@@ -215,25 +215,17 @@ You can verify a finding found by gitleaks using a `git log` command.
 Example output:
 
 ```
-{
-        "Description": "AWS",
-        "StartLine": 37,
-        "EndLine": 37,
-        "StartColumn": 19,
-        "EndColumn": 38,
-        "Match": "\t\t\"aws_secret= \\\"AKIAIMNOJVGFDXXXE4OA\\\"\":          true,",
-        "Secret": "AKIAIMNOJVGFDXXXE4OA",
-        "File": "checks_test.go",
-        "Commit": "ec2fc9d6cb0954fb3b57201cf6133c48d8ca0d29",
-        "Entropy": 0,
-        "Author": "zricethezav",
-        "Email": "thisispublicanyways@gmail.com",
-        "Date": "2018-01-28 17:39:00 -0500 -0500",
-        "Message": "[update] entropy check",
-        "Tags": [],
-        "RuleID": "aws-access-token"
-}
-
+Finding:     aws_secret="AKIAIMNOJVGFDXXXE4OA"
+RuleID:      aws-access-token
+Secret       AKIAIMNOJVGFDXXXE4OA
+Entropy:     3.65
+File:        checks_test.go
+Line:        37
+Commit:      ec2fc9d6cb0954fb3b57201cf6133c48d8ca0d29
+Author:      Zachary Rice
+Email:       z@email.com
+Date:        2018-01-28T17:39:00Z
+Fingerprint: ec2fc9d6cb0954fb3b57201cf6133c48d8ca0d29:checks_test.go:aws-access-token:37
 ```
 
 We can use the following format to verify the leak: