Skip to content

fix(provider): bind policy to runtime hostname - #12

Merged
rldyourmnd merged 2 commits into
mainfrom
fix/runtime-host-identity
Aug 20, 2026
Merged

fix(provider): bind policy to runtime hostname#12
rldyourmnd merged 2 commits into
mainfrom
fix/runtime-host-identity

Conversation

@rldyourmnd

Copy link
Copy Markdown
Contributor

Outcome

Removes the final public/private identity coupling found by the .42 read-only probe and cuts provider v0.1.5-nddev.43.

A public binary no longer contains synthetic example-* host allowlists. It requires exact equality between platform.host and the provider process runtime hostname. This is stricter, estate-neutral and prevents one host policy from executing on another.

Canary evidence

  • .41 was rejected on synthetic subnet coupling and fully rolled back.
  • .42 accepted production private endpoint 10.110.0.5:8443, then refused the private config because public code allowed only example-* hostnames.
  • No .42 active files were installed; this was a read-only provider probe.

Artifact

  • source 1527904a18f23ff652d6425d8f8ef0b8dae91b34
  • provider .43 SHA-256 ccd05a9162297fab5bb7d3bf2e02f299c2ca9092ddc48d556dddb53506462f16
  • two pristine byte-identical static rebuilds

Hosted CI reproduces the exact manifest artifact.

@rldyourmnd
rldyourmnd marked this pull request as ready for review August 20, 2026 11:58
@rldyourmnd
rldyourmnd merged commit ef57a41 into main Aug 20, 2026
6 checks passed
@rldyourmnd
rldyourmnd deleted the fix/runtime-host-identity branch August 20, 2026 11:58
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