jsonld-signatures - npm Package Versions

4.0.1 - 2019-03-28

Changed

• Updated local copy of security-v2 context.

4.0.0 - 2019-02-12

Changed

• NOTE: Updated jsonld to 1.5.0. Dependency and code updates will be required to continue using the native canonize bindings. See the jsonld.js 1.5.0 notes.
• BREAKING: Updated crypto-ld to 3.0.0. The exposed APIs changed the key fingerprint output encodings.
• Switch to eslint.

Added

• Expose useNativeCanonize option in constructors of suites that use rdf-canonize.

3.3.0 - 2019-01-22

Changed

• JwsSignatures now default to verificationMethod term in the proof unless a legacy public key is being used. A legacy public key is one that has the deprecated owner property instead of the newer controller property.

3.2.0 - 2019-01-17

Changed

• Use crypto-ld@2.

Removed

• BREAKING: Remove Node.js 6.x support. If you need Node.js 6.x support please use the 2.x series or setup your own translation.

3.1.2 - 2019-01-08

Fixed

• Fix ProofSet suite matching.
• Ensure proof verification method matches key if given.

3.1.1 - 2019-01-08

Fixed

• Fix ProofSet proof matching.
• Use 2048-bit RSA keys in tests.

Changed

• Improve usage of Babel features.

3.1.0 - 2019-01-04

Fixed

• Move webpack-cli to dev dependency.

Changed

• Update to Babel 7.

3.0.0 - 2019-01-03

Added

• Add compactProof flag that can be set to false to enable skipping compaction of proof(s) when it is known that the input document's (for sign or verify) JSON-LD @context defines all applicable proof terms using the same definitions as the JSON-LD @context used internally by the library (i.e. the JSON-LD @context defined by constants.SECURITY_CONTEXT_URL). This flag should only be set to false by advanced users that have ensured their software systems have strictly validated the input to ensure that it is safe and cannot be misinterpreted. If these guarantees can be met, then setting this flag to false may be a useful optimization consideration.

Changed

• BREAKING: sign and verify APIs require suites and proof purpose instances to be passed.

Removed

• BREAKING: Removed API wrap and injector support.
• BREAKING: callback-based API is no longer supported.
• BREAKING: Removed exposed utility/helper functions.
• Karma PhantomJS support. Upstream deprecated PhantomJS and suggests headless Chrome or similar.

2.3.1 - 2018-09-05

Changed

• Optimize LinkedDataSignature createVerifyData to remove one round of compaction and one round of expansion. This eliminates a total of four rounds (2x compaction, 2x expansion) for sign+verify processes as createVerifyData is used in both sign and verify.

2.3.0 - 2018-03-20

Added

• Add in-browser support for ed25519.