identity: 60 s of clock allowance on starts (validFrom, notBefore) and, the careful way, on revocations; none on ends
A credential issued on a machine whose clock was one second ahead was "not yet valid" at a verifier synchronized by NTP: measured on 2026-09-30 through the Aere Cloud identity route, the first time a credential was issued on one machine and judged on another. Starts (a credential's and a status list's validFrom, a delegation's notBefore) are now accepted up to 60 s in the verifier's future (verifyPresentation clockSkewS, 0..600); a revocation dated up to 60 s ahead already applies; ends (validUntil, notAfter) get no allowance, since that would extend a validity. Tests: identity 44/44, negative control 49/49.
This commit is contained in:
1 parent
aec0ccbead
commit
0b56d8e5df
4 files changed
+42
-11
No files matched your search
+6
-3
@@ -81,7 +81,10 @@ issuer, a bit set in any of them means revoked. A list is decompressed with a ce
|
||||
|
||||
`issuedAt`, `validFrom` and `validUntil` are the issuer's statements; the presentation time is the presenter's, bounded by the
|
||||
verifier's clock (`--max-age`, default 300 s, both ways); a revocation time is the revoker's. Everything is judged on the verifier's
|
||||
clock. For a time the issuer does not choose, notarize: `proofOfCredential` and `proofOfDelegation` (in `identity.mjs`) build AIP-23
|
||||
clock, which is never exactly the issuer's: starts (a credential's or a status list's `validFrom`, a delegation's `notBefore`) are
|
||||
accepted up to 60 s in the verifier's future (`clockSkewS`), and a revocation dated up to 60 s ahead already applies; ends
|
||||
(`validUntil`, `notAfter`) get no allowance, since that would extend a validity. (Measured 2026-09-30: without it, a credential issued
|
||||
on a machine whose clock was a second ahead was "not yet valid" at a verifier synchronized by NTP.) For a time the issuer does not choose, notarize: `proofOfCredential` and `proofOfDelegation` (in `identity.mjs`) build AIP-23
|
||||
envelopes (`identity` and `authorization` kinds of `../proof-kinds`) that the Aere Proof API notarizes and that the AIP-23 reference
|
||||
verifier checks.
|
||||
|
||||
@@ -147,8 +150,8 @@ line is reported as not judged. The private key files are written with mode 0600
|
||||
## Tests
|
||||
|
||||
```
|
||||
node proba-identity.mjs # 43: the paths above, and each attack of the adversarial review as its own test
|
||||
node control-negativ-identity.mjs # on a copy, each of 46 guards removed -> its own named test turns red
|
||||
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-conformitate.mjs # 14: compliance policies judged on real presentations, the record without personal data, the command line
|
||||
node control-negativ-conformitate.mjs # on a copy, each of 13 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
|
||||
|
||||
Reference in new issue
Block a user