conformance: the identity presentation verifier enrolled (134 rules of 10 verifiers, 273 vectors); the reference verifier instruction names all five files beside verify-proof.mjs; module READMEs point to aere.network/tools
This commit is contained in:
1 parent
c9798a0013
commit
5fb38c5d0b
88 files changed
+20246
-179
No files matched your search
+27
-3
@@ -182,6 +182,30 @@ structure (`_sd`, `_sd_alg`, `{"...": digest}`), which would let a holder disclo
|
||||
SD-JWT VC (no `vct`, no type metadata), and no status list inside the token (revocation stays with the AERE credential's list).
|
||||
Checked against the RFC's vectors, not against another SD-JWT library: that is not measured.
|
||||
|
||||
## Named rules
|
||||
|
||||
Since 2026-10-05 every refusal of `verifyPresentation` names its rule. A row is `{ name, pass, detail, rule }`; a row that was not
|
||||
judged is `{ name, pass: null, detail, unjudged }` with its cause. The result carries `rules`, the sorted ids of the rules that
|
||||
refused, and `unjudged`, the sorted causes of what was not judged. The module exports the lists: `REGULI` (37 rules), `NEJUDECATE`
|
||||
(7 causes) and `OPRIRI` (the four rules after whose refusal other checks were not made: `form`, `chain-length`, `delegation-form`,
|
||||
`unreadable`). A time field that cannot be read (a credential's validity, a delegation's or a presentation's bounds) and a malformed
|
||||
earlier link are reported as `unreadable`, which is one of the stopping rules: the checks after it are not made. The verifier does
|
||||
not stop at its first refusal: it makes every check it can reach. `valid` is unchanged: true when
|
||||
no row failed, also when rows were not judged; a caller that needs "nothing left unjudged" reads `unjudged`.
|
||||
|
||||
With these ids the presentation verifier is enrolled in the conformance suite beside this folder (`conformance/`: 37 rules,
|
||||
65 vectors of the artifact kind `identity-presentation`, each rule taken out of a copy of the verifier in turn). SD-JWT, Travel Rule
|
||||
and compliance are not enrolled there.
|
||||
|
||||
Two things changed in behaviour that day, both measured by `proba-identity.mjs`, each with its planting in the negative control:
|
||||
|
||||
- found while the verifier was being enrolled: when the issuer keys in a credential could not be read (for example an Ed25519 key in
|
||||
the `mldsa65` field), the verifier also reported that the holder id is not the id of its keys. The two ids were derived in one
|
||||
step, and the first failure left the second underived. The credential was refused either way; the report named the holder for a
|
||||
fault of the issuer's keys. Each id is now derived on its own;
|
||||
- a `statusLists` or `revocations` argument that is not a list is an error of the caller and throws, like a `trustedIssuers` that
|
||||
is not a list; until then the first two came back as an unreadable presentation.
|
||||
|
||||
## What it does not do
|
||||
|
||||
It does not bind a key to hardware: a device key is a key like any other, and no TPM or secure-enclave attestation is checked here. It
|
||||
@@ -192,14 +216,14 @@ line is reported as not judged. The private key files are written with mode 0600
|
||||
## Tests
|
||||
|
||||
```
|
||||
node proba-identity.mjs # 44: the paths above, and each attack of the adversarial review as its own test
|
||||
node control-negativ-identity.mjs # on a copy, each of 49 guards removed -> its own named test turns red
|
||||
node proba-identity.mjs # 46: the paths above, each attack of the adversarial review as its own test, the named rules
|
||||
node control-negativ-identity.mjs # on a copy, each of 53 guards removed -> its own named test turns red
|
||||
node proba-conformitate.mjs # 15: compliance policies judged on real presentations, the record without personal data, the command line
|
||||
node control-negativ-conformitate.mjs # on a copy, each of 14 guards removed -> its own named test turns red
|
||||
node proba-travel-rule.mjs # 19: two VASPs with registry credentials, the whole exchange, and each attack of the review
|
||||
node control-negativ-travel-rule.mjs # on a copy, each of 19 guards removed -> its own named test turns red
|
||||
node proba-sdjwt.mjs # 23: the RFC 9901 vectors, SD-JWTs issued with AERE keys (EdDSA and ML-DSA-65), each attack
|
||||
node control-negativ-sdjwt.mjs # on a copy, each of 28 guards removed -> its own named test turns red
|
||||
node control-negativ-sdjwt.mjs # on a copy, each of 29 guards removed -> its own named test turns red
|
||||
```
|
||||
|
||||
The envelope test needs the AIP-23 reference verifier (`AERE_VERIFY_PROOF=<verify-proof.mjs>`); without it that test is reported as
|
||||
|
||||
Reference in new issue
Block a user