[A-01] Real secrets are in git history #37

Closed
opened 2026-10-11 20:15:34 -05:00 by pyaniz · 1 comment
Owner

Audit ID: A-01 · Priority: P0 · Effort: M

Real secrets are in git history. .env was committed in 5 commits (2025-12-23 to 2025-12-29, deleted in 2b830d3). It held the Telegram bot token, the Google service-account private key, SECRET_KEY, the BGG token and an admin handle. History exists on origin (all 3 branches) and the github-mirror.yml workflow pushes it to GitHub. Action: rotate every one (BotFather token, Google key, SECRET_KEY, BGG token). Check whether the GitHub mirror is public. Then decide on a history purge (A-03).

Source: AUDIT_FINDINGS.md (audit 2026-10-11). Items marked (verify) need confirming first.

**Audit ID:** A-01 · **Priority:** P0 · **Effort:** M **Real secrets are in git history.** `.env` was committed in 5 commits (2025-12-23 to 2025-12-29, deleted in `2b830d3`). It held the Telegram bot token, the Google service-account private key, `SECRET_KEY`, the BGG token and an admin handle. History exists on `origin` (all 3 branches) and the `github-mirror.yml` workflow pushes it to GitHub. **Action:** rotate every one (BotFather token, Google key, `SECRET_KEY`, BGG token). Check whether the GitHub mirror is public. Then decide on a history purge (A-03). Source: `AUDIT_FINDINGS.md` (audit 2026-10-11). Items marked *(verify)* need confirming first.
Author
Owner

Re-checked 2026-10-24: the secrets are still in git history (.env in 5 commits, Google private key included), but the Telegram bot token, Google service-account key, SECRET_KEY and BGG token have been rotated, so the leaked values are dead. The GitHub mirror is not publicly reachable (404). The remaining history purge is tracked in #39. Closing.

Re-checked 2026-10-24: the secrets are still in git history (.env in 5 commits, Google private key included), but the Telegram bot token, Google service-account key, SECRET_KEY and BGG token have been rotated, so the leaked values are dead. The GitHub mirror is not publicly reachable (404). The remaining history purge is tracked in #39. Closing.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pyaniz/Thursday#37
No description provided.