Skip to content

Latest commit

 

History

History
72 lines (46 loc) · 2.18 KB

CHANGELOG.md

File metadata and controls

72 lines (46 loc) · 2.18 KB
Raw

TweetNaCl.js Changelog

v0.11.1

  • Even faster hash for both short and long inputs (in nacl-fast).

v0.11.0

  • Implement nacl.sign.keyPair.fromSeed to enable creation of sign key pairs deterministically from a 32-byte seed. (It behaves like libsodium's crypto_sign_seed_keypair: the seed becomes a secret part of the secret key.)

  • Fast version now has an improved hash implementation that is 2x-5x faster.

  • Fixed benchmarks, which may have produced incorrect measurements.

v0.10.1

  • Exported undocumented nacl.lowlevel.crypto_core_hsalsa20.

v0.10.0

  • Signature API breaking change! nacl.sign and nacl.sign.open now deal with signed messages, and new nacl.sign.detached and nacl.sign.detached.verify are available.

Previously, nacl.sign returned a signature, and nacl.sign.open accepted a message and "detached" signature. This was unlike NaCl's API, which dealt with signed messages (concatenation of signature and message).

The new API is:

  nacl.sign(message, secretKey) -> signedMessage
  nacl.sign.open(signedMessage, publicKey) -> message | null

Since detached signatures are common, two new API functions were introduced:

  nacl.sign.detached(message, secretKey) -> signature
  nacl.sign.detached.verify(message, signature, publicKey) -> true | false

(Note that it's verify, not open, and it returns a boolean value, unlike open, which returns an "unsigned" message.)

  • NPM package now comes without test directory to keep it small.

v0.9.2

  • Improved documentation.
  • Fast version: increased theoretical message size limit from 2^32-1 to 2^52 bytes in Poly1305 (and thus, secretbox and box). However this has no impact in practice since JavaScript arrays or ArrayBuffers are limited to 32-bit indexes, and most implementations won't allocate more than a gigabyte or so. (Obviously, there are no tests for the correctness of implementation.) Also, it's not recommended to use messages that large without splitting them into smaller packets anyway.

v0.9.1

  • Initial release