Bind readiness receipts to owned TLS and verified source execution - #2871
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fb1f18436b
ℹ️ 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".
twoimo
changed the title
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 228287831e
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5a4498a90c
ℹ️ 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".
1 participant
Readiness receipts could accept caller-controlled TLS trust, execute stale Python bytecode while hashing current source, or reuse an old read-only snapshot. Version-3 receipts now use an isolated source-file launcher that compiles the exact verified Git executor bytes and executes the SQL from the same bundle. Git subprocesses remove inherited overrides and use explicit checkout-derived Git/object directories, and reject file-based alternate object stores. The executor creates its own connection to the fixed project endpoint with the committed Supabase CA; inputs contain credentials only. Both collection paths reject non-idle transactions and verify the new transaction isolation and read-only settings.
Validation: 17 targeted tests pass, including a real PostgreSQL stale-snapshot rejection/readback, a poisoned timestamp-matching bytecode cache with a normal-import control, temporary Git source checks and foreign repository/object-store redirection rejection, credential override rejection, pinned CA handling, bounded CLI failures, and cleanup. Seven reconciliation tests pass after refreshing the manifest. The actual committed source-file launcher also passes source verification. Successful TLS transport tests are mocked; no hosted v3 receipt is claimed.
Addresses the five reviews on this PR and the original provenance findings on #2870. Version-1/2 receipts remain insufficient and cannot be relabeled. Promote through develop and data before resolving the #2870 reviews. This change performs no hosted mutation or production deployment.