Rotate the plaintext credentials found in git history #398
Labels
No labels
bug
enhancement
in-progress
needs-info
needs-triage
p0
ready-for-agent
ready-for-human
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Cloonar/nixos#398
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A full scan of git history turned up ten cleartext credentials, seven of them still live in HEAD, plus eleven committed password hashes.
Every one is readable by anyone with a clone, so deleting the line does not fix it — the blob stays reachable in every clone and on the remote forever. Rotation at the source is the only remediation.
The findings, with path, line and introducing commit, are in
docs/security/git-history-secret-audit.md. Values are deliberately not reproduced there.Priority order:
Cloonar-Multimedia,Cloonar-Smart) — the credentials to the networks every other host sits on. Live in HEAD.buchhaltung.md:2— needs identifying before it can be rotated. Live in HEAD.password. Live in HEAD.hashedPasswordFile+ SOPS, which is the pattern used everywhere else in this repo.Clean results worth recording: no provider API tokens have ever been committed, no private key material, and no unencrypted SOPS file — the ADR-0025 rename was a pure
git mvwith byte-identical blobs.