Skip to content

Preserve and audit credential registry refusal evidence - #156

Merged
Varuas37 merged 22 commits into
mainfrom
codex/ws4-registry-0922
Sep 23, 2026
Merged

Varuas37 merged 22 commits into
mainfrom
codex/ws4-registry-0922

Conversation

@Varuas37

@Varuas37 Varuas37 commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

Corrupt or unsafe credential registries and their lock files now refuse admission with typed, secret-free diagnostics, exact target evidence, and role-specific recovery guidance. Ordinary startup, local provisioning, and offline auth preserve exit policy and audit the refusal without modifying rejected state. A lock refusal does not claim that an unread registry is corrupt or present. Audit delivery failures remain separate reported errors.

Private audit writes retain trusted-root authority through publication and cleanup. Temporary reservations acquire the Windows deletion capability they own; atomic no-replace publication preserves existing records. Directory guarantees distinguish Unix synchronization from Windows file flushing and write-through publication. Recovery guidance prefers restoring verified registry backups; lock repair never instructs registry reinitialization.

Relates to #113. This draft is not merge-cleared and does not close the issue. Round 3 findings led to a recorded structural diagnosis and revised ownership of cleanup capability, refusal transitions, and adversarial test setup. Final independent review remains pending.

Current revision validation is pending in the isolated local build queue and CI. It adds native Windows cleanup tests, valid/absent-registry unsafe-lock tests, and corrected ancestry-redirection tests with a complete malicious path. A controlled old-cleanup negative run must fail before the fixed-source validation is accepted.

Earlier revision validation (not proof for this new revision): strict all-target clippy for local-storage/auth/server; 9 local-storage tests, 62 auth unit and 3 integration tests, 8 real-process refusal tests, 32 server core tests, and architecture checks passed. Its CI passed seven checks; Windows exposed a path-display assertion mismatch corrected here while preserving exact typed target assertions.

Current formatting, architecture, and diff checks pass. Windows execution awaits CI. No power-loss testing or crash-durability proof is claimed. Shared journal-transaction APIs for the installer are a separate follow-up.

Preserve corrupt credential registries and emit actionable, secret-free diagnostics with durable refusal evidence across gateway startup, automatic provisioning, and offline auth commands. Keep audit sink failure beside the primary registry fault without changing exit or restart policy.\n\nThis repairs the unsafe diagnostic gap introduced by eac1ead (Commit credential lifecycle evidence with the registry state (#68)).\n\nAddresses #113
Translate unsafe registry files into the audited refusal path and publish refusal records only through trusted-root storage operations. Sync each audit directory parent before descending so a failed ancestry publication cannot be mistaken for durable evidence.\n\nAdd process regressions for unsafe files, symlink escape attempts, offline attribution, and the separate managed recovery record.
Create nested private directories beneath a trusted root one component at a time. Sync each established parent before descent and the final leaf before returning so audit sinks share one publication contract.\n\nUse the primitive for credential-registry refusal evidence and keep the sink's symlink escape regression.
Select one platform implementation for non-UTF registry paths so strict linting sees no unreachable fallback while preserving lossless audit targets.
Build adapter fixtures beneath an explicitly private auth directory so they exercise the same trusted-root contract as composition.
@Varuas37
Varuas37 marked this pull request as ready for review September 23, 2026 03:02
@Varuas37
Varuas37 merged commit ff8362c into main Sep 23, 2026
8 checks passed
@Varuas37
Varuas37 deleted the codex/ws4-registry-0922 branch September 23, 2026 03:02

@greptile-apps greptile-apps 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.

Your trial has ended. Reactivate Greptile to resume code reviews.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 23, 2026 •

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-23T03:04:21.016666Z 7458e06 Draft marked ready
ℹ️ 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.

Varuas37 pushed a commit that referenced this pull request Nov 9, 2026
nessa_ui#156 merged as 2b5bba0, which holds the same tree as the branch
head this PR was checked against (the last commit there only added a
registry dependency).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JcBpmVHPWxktA9QurvUMjM
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant