@openvtc/trust-tasks 0.18.4 → 0.18.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +37 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -11,6 +11,43 @@ The package versions over **its own API** — what a consumer compiles against
|
|
|
11
11
|
not over `SPEC.md`. Below 1.0 a breaking change bumps the leading non-zero
|
|
12
12
|
component.
|
|
13
13
|
|
|
14
|
+
## 0.18.5 — 2026-09-10
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
### Specifications
|
|
18
|
+
|
|
19
|
+
- **process-attestation**: Bind the response to the artifact that was asked about (#435)
|
|
20
|
+
|
|
21
|
+
Verifier conformance pinned the challenge but never the artifact. A
|
|
22
|
+
Holder that holds a receipt for artifact B and none for artifact A could
|
|
23
|
+
answer a request about A with result "attested", artifact B, and a
|
|
24
|
+
genuinely valid receipt for B. Every signature in that exchange
|
|
25
|
+
verifies - the envelope proof is the Holder's, the challenge is the one
|
|
26
|
+
the Verifier sent, and the receipt is authentic under its own
|
|
27
|
+
primitive - so a Verifier implementing exactly the four published rules
|
|
28
|
+
concludes that A was attested. Only the subject was swapped.
|
|
29
|
+
|
|
30
|
+
The response prose said artifact "repeats the requested digest", but
|
|
31
|
+
that was descriptive, and nothing on the Verifier side compared it.
|
|
32
|
+
|
|
33
|
+
Adds two Verifier rules: reject a response whose artifact does not match
|
|
34
|
+
the one supplied, and do not rely on assessment unless the receipt binds
|
|
35
|
+
that same artifact. The first rejects the response before the receipt is
|
|
36
|
+
fetched; the second catches a response that echoes A faithfully while
|
|
37
|
+
the receipt underneath binds B. Neither is expressible in the payload
|
|
38
|
+
schema, because the request is not in the response document's scope, so
|
|
39
|
+
they are stated as conformance rules and explained in Security &
|
|
40
|
+
Privacy.
|
|
41
|
+
|
|
42
|
+
Also makes the Holder's artifact echo normative rather than implied,
|
|
43
|
+
mirroring the existing challenge echo. The schema already requires
|
|
44
|
+
artifact on both result branches, so this constrains no wire shape that
|
|
45
|
+
was previously free.
|
|
46
|
+
|
|
47
|
+
Prose only: no schema change, and regenerating both libraries produces
|
|
48
|
+
no diff. In place in 0.1 per SPEC 5.2 - the specification is draft, so
|
|
49
|
+
its prose may change without notice.
|
|
50
|
+
|
|
14
51
|
## 0.18.4 — 2026-09-10
|
|
15
52
|
|
|
16
53
|
|