SecurityThe verifier returns only what was asked for, the wallet core ties registration to the signer, packages 0.8.3
Changed
- The @tamga-network/* packages are on npm as the 0.8.3 test release; the stable 1.0.0 comes when everything is ready.
Security
- The verifier now returns only the fields the verification policy asks for. The technical fields of a document and anything the wallet disclosed beyond the request are no longer in the result.
- The verifier limits how far a revocation list may run ahead of its last anchor. When the list is newer than the latest anchor by more than one hour (the default), the result is “undetermined” instead of a decision. A site that verifies on its own server should reload the anchors more often than that.
- The wallet core can tie a verifier's registration certificate to the certificate that signed the request. A self-signed certificate that copies a registered organisation's identifier no longer counts as that organisation.
- The wallet core refuses http addresses by default, both in a document offer and in the address it returns to after a presentation. Local development needs an explicit option.
- The trust list publisher stops when a record of the previously published list is missing from the new one or when a history row was changed. A removal goes through only with an approved entry that is bound to one list version.
Applications built on the wallet core have to be updated, not only the package. For a local development server pass allowLocalDevHost. To get the registration certificate check pass signerTrust, and do not accept a result that says signerTrusted: false. When a document is issued after an identity presentation and the result comes back to the app's own address, pass that address as callbackUri. The steps are in the package changelog, in the 0.8.3 section.