commit history
The full chain of commits in a repository, which keeps every past version of every file, including deleted secrets.
In more detail
Deleting a leaked key changes only the latest version; every clone, fork and cache still has the commit. Revoke and rotate the key first, then rewrite history with a tool such as git filter-repo.
Related terms
- Git — A free, open-source distributed version control system that records the history of a project as a chain of snapshots.
- key rotation — Replacing a password or key with a new one on a schedule or after a suspected leak, and re-encrypting what it protected.
- working tree — The files of a Git repository as they currently exist on disk, which you edit before staging and committing.
- commit — A saved snapshot of the whole project in Git, together with its author, committer, time, message and a pointer to the commit before it.
- secret scanning — Searching code, commits and files for credentials such as keys and tokens, ideally before they are committed.
Taught in
- Shift-Left Security Principles & Automated Pipeline Gates — Cloud Security & DevSecOps Engineering
- Pre-Commit Secret Scanning with Gitleaks & Entropy — Cloud Security & DevSecOps Engineering
- Why Secrets Leak — Application Security & Threat Modeling for Engineers
- Secret Scanning — Application Security & Threat Modeling for Engineers