Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Scanning a file containing a HashiCorp Vault access token with ggshield passes clean. The client does the scanning but the detection patterns live in GitGuardian's server-side detection engine, which simply had no pattern for this token shape.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Fixed server-side in GitGuardian's detection engine, no client update needed. If Vault tokens are slipping through an older scan, the fix is already live in the current engine.
Source: https://github.com/GitGuardian/ggshield/issues/459
Source: https://github.com/GitGuardian/ggshield/issues/459
Shows how to fix ggshield does not flag HashiCorp Vault tokens as secrets. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Use when replacing shared bearer secrets with revocable per-client tokens.
Shows how to fix azure Key Vault CSI driver driver name secrets-store.csi.k8s.io not found after AKS node upgrade. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.