website/node_modules/tweetnacl/CHANGELOG.md

TweetNaCl.js Changelog

v0.14.5

v0.14.4

v0.14.3

Fixed a bug in the fast version of Poly1305 and brought it back.

Thanks to @floodyberry for promptly responding and fixing the original C code:

"The issue was not properly detecting if st->h was >= 2^130 - 5, coupled with [testing mistake] not catching the failure. The chance of the bug affecting anything in the real world is essentially zero luckily, but it's good to have it fixed."

https://github.com/floodyberry/poly1305-donna/issues/2#issuecomment-202698577

v0.14.2

Switched Poly1305 fast version back to original (slow) version due to a bug.

v0.14.1

No code changes, just tweaked packaging and added COPYING.txt.

v0.14.0

If want to continue using them, you can include https://github.com/dchest/tweetnacl-util-js package:

  <script src="nacl.min.js"></script>
  <script src="nacl-util.min.js"></script>

or

  var nacl = require('tweetnacl');
  nacl.util = require('tweetnacl-util');

However it is recommended to use better packages that have wider compatibility and better performance. Functions from nacl.util were never intended to be robust solution for string conversion and were included for convenience: cryptography library is not the right place for them.

Currently calling these functions will throw error pointing to tweetnacl-util-js (in the next version this error message will be removed).

v0.13.3

No code changes.

v0.13.2

v0.13.1

v0.13.0

v0.12.2

v0.12.1

v0.12.0

v0.11.2

v0.11.1

v0.11.0

v0.10.1

v0.10.0

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.)

v0.9.2

v0.9.1



JohnCoene/chirp documentation built on May 25, 2021, 6:33 p.m.