Harden Codex auth redaction policy #129

Closed
opened 2026-06-02 03:58:02 -04:00 by didericis-codex · 0 comments
Collaborator

Problem

Issue #117 identifies bot_bottle/codex_auth.py as a remaining security-sensitive hotspot. Its dummy auth generation and redaction behavior depend on schema knowledge and heuristics. Future Codex auth.json fields could accidentally survive redaction if they do not match the current token/secret/key naming patterns.

Desired outcome

Add a PRD for making Codex auth redaction policy explicit and coverage-driven. The PRD should cover allowlist vs denylist behavior, nested JWT/auth claim handling, regression fixtures, and failure behavior for unknown sensitive-looking fields.

Parent context

Carved out from the broader hotspot review in #117.

## Problem Issue #117 identifies `bot_bottle/codex_auth.py` as a remaining security-sensitive hotspot. Its dummy auth generation and redaction behavior depend on schema knowledge and heuristics. Future Codex `auth.json` fields could accidentally survive redaction if they do not match the current token/secret/key naming patterns. ## Desired outcome Add a PRD for making Codex auth redaction policy explicit and coverage-driven. The PRD should cover allowlist vs denylist behavior, nested JWT/auth claim handling, regression fixtures, and failure behavior for unknown sensitive-looking fields. ## Parent context Carved out from the broader hotspot review in #117.
didericis added the Kind/EnhancementKind/Security labels 2026-06-02 04:05:27 -04:00
didericis-codex was assigned by didericis 2026-06-02 04:05:34 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: didericis/bot-bottle#129