Skip to content

rustsdcmcp v0.7.0

Latest

Choose a tag to compare

@fastrevmd-lab fastrevmd-lab released this 10 Nov 03:45
· 2 commits to main since this release
v0.7.0
07621ea

Security

  • Bumps rmcp to 3.9.0 for RUSTSEC-2026-0462. The advisory is in rmcp's
    Streamable HTTP client, which this server does not use. (#307)
  • The image's distroless/cc-debian13 runtime base moves to cc66d22, which
    carries zlib 1.3.1-1+deb13u1 for CVE-2026-76844 and CVE-2026-85091. The
    v0.6.0 image's zlib is affected. (#302, #308)

Added

  • prepare_sdc_ips_rule_batch: plan 1-32 IPS rule and exempt-rule creates,
    updates and deletes inside one profile as a single change set, bound by one
    digest over every write in order, and approved once. It is applied through
    the existing apply_sdc_ips_write. Before, building out a profile took one
    prepare → approve → apply round trip per rule. Every write keeps the guards
    and drift check of prepare_sdc_ips_write. The writes together may
    reference at most 256 distinct signatures, checked before prepare's first
    read. Apply runs the client's body checks and re-checks every target before
    sending anything, then sends the writes in order and stops at the first
    failure. The new writes field gives each write's status (applied,
    rejected, unknown, not_attempted). SDC cannot undo earlier writes as a
    unit, so a later write's definitive rejection records the operation
    Failed. The owner clears it with discard_sdc_operation, which reverts
    nothing and keeps the failure details, then finishes or undoes the
    remainder. A later write with an unknown outcome is
    Indeterminate, as for a single write. get_sdc_change_set_details returns
    the batch's plan_digest. Signatures, profiles, and deletes that need a
    reference scan stay one per change set. Like every write tool, it is
    excluded from a wildcard tool scope, so a token must name it.
  • apply_sdc_ips_write results gain writes (per-write status and any
    created UUID), and validation gains write_count. A one-write change set's
    plan, digest, and other fields are unchanged.

Changed

  • Refreshed the vendored SDC OpenAPI export and docs/sdc-api/endpoints.md
    (368 -> 377 operations). No client or tool change. The changed operations
    are a widened description limit (255 -> 999) on a shared schema, plus
    additive gbp_tags on firewall rules and interfaces on device zones. The 9
    added operations (L2 cluster deployments and a cluster interface status read)
    are not implemented. The new MNHA BFD session_type (multihop/singlehop)
    is exempted from key redaction so it isn't masked as a session secret. (#300)

Fixed

  • SdcConfig's Debug output showed the egress_proxy URL in full, including any credentials in it. It now shows only the proxy's origin (scheme, host, port). No shipped code path printed the config, so nothing leaked.

Dependencies

  • rmcp 3.7.0 -> 3.8.0, rustix 1.1.5 -> 1.1.6 (#304); axum-server
    0.8.0 -> 0.9.0 (#311); uuid 1.29.0 -> 1.29.2, toml 1.1.8 -> 1.2.1 (#312)
  • rust builder image updated (#301)
  • Release workflows: mecmcp reusable workflows v0.28.2 -> v0.32.0,
    docker/login-action 4.7.0 -> 4.8.0; the package-conformance action
    v0.30.1 -> v0.32.0 (#303, #309)