docs: Tower request-auth design decision (post-#1421) + README Upgrading section - #1377
Merged
Conversation
waleedkadous
changed the title
waleedkadous
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two doc additions:
arch.md Key Design Decision 8 — records Tower's request-authentication model as it stands after the GHSA-xvjp-7748-v88v hardening (PR Enforce request authentication on the Tower local API #1421, the shared local key on every non-public route): key generation and transport, the narrow public allowlist, the complementary tunnel-origin restrictions from PR [#1370] Fix tunnel path bypass that let a remote request deregister the tower #1374, and the honest trust-boundary caveat. The original version of this PR recorded the issue tower: no internal authentication — any request reaching the tunnel reaches every Tower endpoint; all auth lives at the codevos.ai edge #1375 no-internal-auth ruling; that ruling was superseded nine days later by the advisory work, so it now appears as an explicitly-marked superseded note rather than as current guidance.
README Upgrading section — adopter-requested: documents that upgrading is two steps (global npm install + per-project
codev update), why skipping step 2 causes 'agents stopped following the protocol' reports, VS Code extension update path, and the Tower restart note.🤖 Generated with Claude Code