Skip to content

[WRONG BRANCH] security: remove account-identifying screenshots and sanitize live-verification notes - #468

Closed
luvs01 wants to merge 1 commit into
mainfrom
codex/propose-fix-for-oauth-email-disclosure
Closed

[WRONG BRANCH] security: remove account-identifying screenshots and sanitize live-verification notes#468
luvs01 wants to merge 1 commit into
mainfrom
codex/propose-fix-for-oauth-email-disclosure

Conversation

@luvs01

@luvs01 luvs01 commented Sep 7, 2026

Copy link
Copy Markdown
Owner

Motivation

  • A live-verification run copied real auth.json state and two committed GUI screenshots contained unredacted OAuth account email addresses, creating an information-disclosure risk.
  • The change removes the identifying assets and strips operational provenance from the verification record while preserving the non-sensitive verification outcome.

Description

  • Deleted the two account-identifying images from devlog/_plan/260904_provider_quota_refresh/assets/ (030_accounts_refresh_button.png, 040_accounts_refresh_result.png).
  • Sanitized devlog/_plan/260904_provider_quota_refresh/031_live_verification_record.md to remove references to the operator's local home, the copied auth.json provenance, and the pooled-account details, and to note only that an isolated scratch instance was used and deleted.
  • Removed the corresponding reference from devlog/_plan/260904_provider_quota_refresh/030_wp3_live_verification_and_pr.md so the capture plan no longer points at the removed assets.
  • Kept non-sensitive quota/usage screenshots and preserved the wire/UI evidence of the quota-refresh feature.

Testing

  • Ran bun run privacy:scan and observed Privacy scan passed.
  • Ran git diff --check and git diff --stat to verify the patch and found no whitespace or diff errors.
  • Searched the tree with rg for the removed asset names and operational provenance strings and confirmed they no longer appear in the current tree.
  • Committed the remediation as security: remove account-identifying screenshots and verified git status --short --branch shows a clean working tree.

Codex Task

@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

Deterministic PR hygiene checks passed.

@github-actions github-actions Bot changed the title security: remove account-identifying screenshots and sanitize live-verification notes [WRONG BRANCH] security: remove account-identifying screenshots and sanitize live-verification notes Sep 7, 2026
@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

⏳ DRAFT

  • wrong target branch (main); retarget to dev.

What to do

  • Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.

@github-actions
github-actions Bot marked this pull request as draft September 7, 2026 08:08
@coderabbitai

coderabbitai Bot commented Sep 7, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: 8a6d99e3-ae7b-499d-bdfc-fdcdb43a4794


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 47c3114f77

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +8 to +10
Verification ran against an isolated scratch instance on port 10399, started with
`bun run src/cli/index.ts start --port 10399` from this worktree. The scratch home was
deleted when verification finished.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Purge identifying screenshots from reachable history

Sanitizing this record and deleting the files only removes them from the new tree; the account-identifying images remain directly retrievable from parent bba63222 (for example, git show 8a28a7d^:devlog/_plan/260904_provider_quota_refresh/assets/030_accounts_refresh_button.png), which remains an ancestor of this commit and therefore preserves the disclosure for every clone. Rewrite the affected reachable history and coordinate removal of hosted PR/cache refs, rather than treating this tip-only deletion as completed remediation.

AGENTS.md reference: AGENTS.md:L122-L127

Useful? React with 👍 / 👎.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-07T08:11:14.384117Z 47c3114 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@luvs01

luvs01 commented Sep 7, 2026

Copy link
Copy Markdown
Owner Author

Superseded by a focused cleanup of the same four files, with the historical verification outcomes preserved. No independent change remains in this proposal.

@luvs01 luvs01 closed this Sep 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant