Skip to content

fix: attest only bound Docker host ports - #225

Open
Joncallim wants to merge 1 commit into
codex/68-npm-provenancefrom
codex/68-docker-port-publication-truthfulness
Open

fix: attest only bound Docker host ports#225
Joncallim wants to merge 1 commit into
codex/68-npm-provenancefrom
codex/68-docker-port-publication-truthfulness

Conversation

@Joncallim

@Joncallim Joncallim commented Sep 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • Retain private container ports as Docker listener topology, but leave their Exposes edges without publication evidence.
  • Mint DockerPortPublication only for the bounded nonzero host-port to container-port protocol collector grammar.
  • Share the closed discriminant with the internal-network host-publication finding.

Verification

  • cargo fmt --check (from crates)
  • cargo test -p dockermap-core
  • cargo test -p dockermap-daemon
  • cargo clippy --workspace --all-targets -- -D warnings

No API, UI, schema, or contract artifact change: the wire model already carries bounded collector port strings and evidenceRefs permits empty lists for relationships without a direct attestation.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 2, 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-02T14:05:27.442088Z 45e9227 PR opened
ℹ️ 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.

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 45e9227145

ℹ️ 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".

Comment on lines +533 to +544
evidence_refs: is_host_published_docker_port(port)
.then(|| {
docker_runtime_evidence(
snapshot,
&source,
&listener_id,
RuntimeEvidenceKind::DockerPortPublication,
evidence_provider_revision,
)
})
.into_iter()
.collect(),

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Distinguish private-port evidence from migration state

When Docker reports a private-only port such as 80/tcp, this creates an Exposes edge with an empty evidenceRefs; however, the runtime inspector renders every empty list as “this relationship family is still migrating,” and the model/docs reserve that state for relationship families not yet migrated. Users inspecting a Docker-observed private port therefore receive an incorrect provenance explanation. Represent private-port exposure with an appropriate bounded evidence kind, or update the contract and UI to distinguish deliberately unattested edges from migration state.

AGENTS.md reference: AGENTS.md:L56-L57

Useful? React with 👍 / 👎.

@Joncallim
Joncallim force-pushed the codex/68-docker-port-publication-truthfulness branch from 45e9227 to 4701281 Compare September 2, 2026 14:06
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