@openvtc/trust-tasks 0.26.6 → 0.26.7
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 +38 -0
- package/dist/_shared/components.d.ts +2 -2
- package/dist/_shared/components.d.ts.map +1 -1
- package/dist/device/list/0.1/payload.d.ts +4 -4
- package/dist/device/list/0.1/payload.d.ts.map +1 -1
- package/dist/device/list/0.1/payload.js +4 -2
- package/dist/device/list/0.1/payload.js.map +1 -1
- package/dist/device/list/0.2/payload.d.ts +4 -4
- package/dist/device/list/0.2/payload.d.ts.map +1 -1
- package/dist/device/list/0.2/payload.js +4 -2
- package/dist/device/list/0.2/payload.js.map +1 -1
- package/dist/device/register/0.1/payload.d.ts +4 -4
- package/dist/device/register/0.1/payload.d.ts.map +1 -1
- package/dist/device/register/0.1/payload.js +4 -2
- package/dist/device/register/0.1/payload.js.map +1 -1
- package/dist/device/register/0.2/payload.d.ts +4 -4
- package/dist/device/register/0.2/payload.d.ts.map +1 -1
- package/dist/device/register/0.2/payload.js +4 -2
- package/dist/device/register/0.2/payload.js.map +1 -1
- package/dist/index.d.ts +1 -0
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +1 -0
- package/dist/index.js.map +1 -1
- package/dist/vta/witness/request/0.1/payload.d.ts +597 -0
- package/dist/vta/witness/request/0.1/payload.d.ts.map +1 -0
- package/dist/vta/witness/request/0.1/payload.js +311 -0
- package/dist/vta/witness/request/0.1/payload.js.map +1 -0
- package/package.json +1 -1
- package/src/_shared/components.ts +4 -2
- package/src/device/list/0.1/payload.ts +4 -2
- package/src/device/list/0.2/payload.ts +4 -2
- package/src/device/register/0.1/payload.ts +4 -2
- package/src/device/register/0.2/payload.ts +4 -2
- package/src/index.ts +1 -0
- package/src/vta/witness/request/0.1/payload.ts +405 -0
package/CHANGELOG.md
CHANGED
|
@@ -11,6 +11,44 @@ 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.26.7 — 2026-10-15
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
### Added
|
|
18
|
+
|
|
19
|
+
- **vta/witness**: Vta/witness/request — the VTA runs a witnessed session for its principal's relationship (#777)
|
|
20
|
+
|
|
21
|
+
A Verifiable Witness Credential is issued to the participating party of a
|
|
22
|
+
witness/session, who presents its relationship credential bound to the
|
|
23
|
+
session's challenge. A principal whose keys and credentials live in a VTA
|
|
24
|
+
cannot do that from a client that holds neither. This adds
|
|
25
|
+
vta/witness/request/0.1: the client names a witness, the relationship
|
|
26
|
+
(relationshipDid, counterpartyDid, the enclosing thread) and credentials by
|
|
27
|
+
vault handle; the VTA opens the session as the relationship DID, builds and
|
|
28
|
+
signs the presentation itself, submits, verifies the VWC as a verifier of
|
|
29
|
+
the evidence would (issuer = session recipient = response signer,
|
|
30
|
+
taskContext/taskDigest over the session document as sent, subject and
|
|
31
|
+
object digest, vwcDigestMultibase), and stores it in the credential vault
|
|
32
|
+
with its evidence — the session document as sent and the submit #response
|
|
33
|
+
as received. It answers with the vault handle, the digest and the two
|
|
34
|
+
evidence documents (which carry the VWC); never a key, a presentation or
|
|
35
|
+
the challenge.
|
|
36
|
+
|
|
37
|
+
Membership evidence is optional. A VMC naming the relationship DID rides
|
|
38
|
+
in the relationship presentation; one naming a member DID needs an
|
|
39
|
+
explicit memberDid, and the VTA builds a second presentation by that DID
|
|
40
|
+
bound to the same session. witness/session/submit/0.1 has no member for
|
|
41
|
+
it, so its carriage is the witness's own (SPEC 4.5.1 leaves an ext
|
|
42
|
+
namespace's semantics to its controller); the OpenVTC carriage is cited
|
|
43
|
+
non-normatively.
|
|
44
|
+
|
|
45
|
+
Authorization is standing over every context the task touches, expressed
|
|
46
|
+
as the new witnessRequest capability (witness-request in device/_shared
|
|
47
|
+
0.1), which is not sign and is not satisfied by sign. Errors: notFound,
|
|
48
|
+
credentialMismatch, noMatchingProtocol, witnessUnreachable (retryable),
|
|
49
|
+
witnessRefused, challengeMismatch, presentationInvalid (the witness's own
|
|
50
|
+
code and message in details), vwcInvalid.
|
|
51
|
+
|
|
14
52
|
## 0.26.6 — 2026-10-15
|
|
15
53
|
|
|
16
54
|
|
|
@@ -396,11 +396,11 @@ export type Capability_AclV0_2 = string;
|
|
|
396
396
|
/**
|
|
397
397
|
* Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything.
|
|
398
398
|
*/
|
|
399
|
-
export type Capability_DeviceV0_1 = "vault-read" | "vault-write" | "proxy-login" | "fill-release" | "policy-admin" | "device-admin" | "sign" | "key-mint" | "sign-trust-task" | "credential-write" | "memory-read" | "memory-write" | "room-present" | "room-open" | "key-export" | "sign-sshsig" | "sign-jws" | "sign-csr" | "external-accounts-manage" | "external-auth-use" | "pcs-vetter" | "pcs-applicant";
|
|
399
|
+
export type Capability_DeviceV0_1 = "vault-read" | "vault-write" | "proxy-login" | "fill-release" | "policy-admin" | "device-admin" | "sign" | "key-mint" | "sign-trust-task" | "credential-write" | "memory-read" | "memory-write" | "room-present" | "room-open" | "key-export" | "sign-sshsig" | "sign-jws" | "sign-csr" | "external-accounts-manage" | "external-auth-use" | "pcs-vetter" | "pcs-applicant" | "witness-request";
|
|
400
400
|
/**
|
|
401
401
|
* Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything.
|
|
402
402
|
*/
|
|
403
|
-
export type Capability_DeviceV0_2 = "vaultRead" | "vaultWrite" | "proxyLogin" | "fillRelease" | "policyAdmin" | "deviceAdmin" | "sign" | "keyMint" | "signTrustTask" | "credentialWrite" | "memoryRead" | "memoryWrite" | "roomPresent" | "roomOpen" | "keyExport" | "signSshsig" | "signJws" | "signCsr" | "externalAccountsManage" | "externalAuthUse" | "pcsVetter" | "pcsApplicant";
|
|
403
|
+
export type Capability_DeviceV0_2 = "vaultRead" | "vaultWrite" | "proxyLogin" | "fillRelease" | "policyAdmin" | "deviceAdmin" | "sign" | "keyMint" | "signTrustTask" | "credentialWrite" | "memoryRead" | "memoryWrite" | "roomPresent" | "roomOpen" | "keyExport" | "signSshsig" | "signJws" | "signCsr" | "externalAccountsManage" | "externalAuthUse" | "pcsVetter" | "pcsApplicant" | "witnessRequest";
|
|
404
404
|
/**
|
|
405
405
|
* Number of chunks in the bundle, equal to ceil(expectedSizeBytes / chunkSize). Bounded at 4096 so that the manifest itself — one digest per chunk — fits in the single document that carries it under the same message-size reasoning as a chunk.
|
|
406
406
|
*/
|