Skip to content

chore(deps): take affinidi-did-resolver-cache-sdk 0.8.39 — a deactivated did:webvh issuer is refused - #37

Merged
stormer78 merged 1 commit into
mainfrom
chore/cache-sdk-0.8.39
Oct 1, 2026
Merged

stormer78 merged 1 commit into
mainfrom
chore/cache-sdk-0.8.39

Conversation

@stormer78

Copy link
Copy Markdown
Contributor

Why

SEC-4045 / VGI-04. Before affinidi-did-resolver-cache-sdk 0.8.39 (affinidi/affinidi-tdk-rs#907), resolving a did:webvh whose log ends in a deactivation entry returned the last DID document as Ok, with its keys still in it.

The gateway's proof verifier (src/proof.rs, IssuerKeys::resolve_vm_for_purpose) resolves the issuer through the cache SDK and takes the signing key from the document it gets back. So on 0.8.38 the gateway accepts a push/provision / push/wake proof signed by a deactivated did:webvh issuer.

With 0.8.39, resolving a deactivated did:webvh fails. The verifier already treats any resolution failure as a final refusal ("could not resolve the proof issuer's DID document"), so no code change is needed. did-scid 0.2.8 does the same for did:scid:vh.

src/tsp.rs check_advertised only logs a warning when resolution fails, so this change doesn't affect what it does.

What

  • Cargo.toml: affinidi-did-resolver-cache-sdk floor goes from 0.8.38 to 0.8.39. A comment next to the existing 0.8.37 SSRF note explains why this is a floor.
  • Cargo.lock: only the two targeted packages were updated (cargo update -p affinidi-did-resolver-cache-sdk -p did-scid).

Lockfile changes

package from to
affinidi-did-resolver-cache-sdk 0.8.38 0.8.40 (highest compatible on crates.io)
did-scid 0.2.7 0.2.8

No other package moved. The graph has one copy of each.

Verification

All run locally on Rust 1.99.0 (+stable, which matches CI's stable), with RUSTFLAGS="-D warnings" as CI sets it:

  • cargo fmt --all -- --check: ok
  • cargo clippy --all-targets -- -D warnings: ok
  • cargo test --all-targets: ok, 141 passed (84 lib, 25 + 32 integration), 0 failed
  • cargo deny check: advisories, bans, licenses and sources all ok

No regression test is added. The existing IssuerKeys / document-auth tests use did:key issuers with a default resolver. A loopback deactivated-did:webvh test would need new infrastructure: a dev-dependency to build and sign a webvh log with a deactivation entry, a local HTTP server, and a HostPolicy opt-out. That is out of proportion to a dependency bump. The behaviour is covered upstream in affinidi/affinidi-tdk-rs#907.

Compatibility

No API or source changes. The only change in behaviour is the intended one: a deactivated did:webvh / did:scid:vh issuer can no longer authorise provision or wake.

…ted did:webvh issuer is refused

SEC-4045 / VGI-04. Before affinidi-did-resolver-cache-sdk 0.8.39
(affinidi/affinidi-tdk-rs#907), resolving a did:webvh whose log ends in a
deactivation returned the last DID document as Ok, keys included. The proof
verifier (src/proof.rs, IssuerKeys::resolve_vm_for_purpose) takes the issuer
key from that document, so on 0.8.38 it accepted a deactivated did:webvh
issuer's signature. 0.8.39 makes that resolution fail, and the verifier
already turns any resolution failure into a final refusal, so no source
change is needed. did-scid 0.2.8 does the same for did:scid:vh.

Raise the Cargo.toml floor to 0.8.39 and update only the two packages:
affinidi-did-resolver-cache-sdk 0.8.38 -> 0.8.40 (highest compatible),
did-scid 0.2.7 -> 0.2.8. Nothing else in Cargo.lock moves.

cargo +stable fmt --all -- --check, clippy --all-targets -- -D warnings,
test --all-targets (141 tests) and cargo deny check all pass on Rust 1.99.

Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
@stormer78
stormer78 merged commit 4434212 into main Oct 1, 2026
3 checks passed
@stormer78
stormer78 deleted the chore/cache-sdk-0.8.39 branch October 1, 2026 15:15
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