docs: pin loopback in the README config and scope the tpm row to 0.3.0 - #475
Merged
Conversation
Both halves are the same defect: the tree is correct and the release a
reader installs is not, and the docs describe the tree.
listen_addr The Quick Start config omitted listen_addr and the
Configuration reference documented "0.0.0.0:8443". On the
published 0.3.0 the default is unconditionally
0.0.0.0:8443 and there is no loopback guard, while
CMCP_DEV_MODE=1 skips the bearer token on purpose. So
following the README on 0.3.0 stands up an
unauthenticated policy gateway on every interface. main
already defaults to loopback in tokenless dev mode and
raises ConfigError on a non-loopback bind, so pinning
127.0.0.1 explicitly is correct on both. The quickstart
page was fixed for this; the README was not.
tpm row STATUS.md credited report-signature verification as
hardware-validated. verify_tpm_quote_chained was
validated on 2026-07-31, but it had no production caller:
the tpm2 branch of verify_trace_claim called only
verify_tpm_measurement, which takes no signature
parameter, so a forged TPMS_ATTEST with correct magic and
matching qualifying_data was reported as
hardware-attested (#370, fixed in #469, ships in 0.4.0).
The row now says so and points TPM evaluators at main.
The #431 chain caveat is unchanged and still applies
after the fix.
Also links agentrust-io.com/quickstart from Quick Start. The repo is the
landing page for readers who never reach the docs site.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Both halves are the same defect in different files: the tree is correct, the release a reader installs is not, and the docs describe the tree. Surfaced by HN traffic landing on the repo, where the README is the only thing a visitor reads.
listen_addrThe Quick Start config omitted
listen_addr, and the Configuration reference documented"0.0.0.0:8443"outright.mainlisten_addrdefault0.0.0.0:8443, unconditionalConfigErrorCMCP_DEV_MODE=1skips the bearer token requirement on purpose. So following the README on 0.3.0 stands up an unauthenticated policy gateway on every interface. Verified by unpacking the publishedcmcp_runtime-0.3.0-py3-none-any.whl:config.pyhaslisten_addr: str = "0.0.0.0:8443"and no_is_loopback_hostat all.Pinning
127.0.0.1:8443explicitly is correct on both versions, so this needs no release to take effect. The quickstart page was fixed for exactly this; the README was not.tpmrow in STATUS.mdThe row credited report-signature verification as hardware-validated.
verify_tpm_quote_chainedwas validated on 2026-07-31, but it had no production caller: thetpm2branch ofverify_trace_claimcalled onlyverify_tpm_measurement, which takes no signature parameter, so a forgedTPMS_ATTESTwith correct magic and matchingqualifying_datawas reported as hardware-attested. That is #370, fixed in #469, shipping in 0.4.0.The row now leads with "Not in 0.3.0", separates the validated function from the shipped code path, and points TPM evaluators at
main. The #431 chain caveat is unchanged and still applies after the fix.Also
Links agentrust-io.com/quickstart from Quick Start. The repo is the landing page for anyone who never reaches the docs site.
Docs only, no code changes. Independent of #470, so it can merge without waiting on the agt-core pin.
🤖 Generated with Claude Code