Dmitry Chestnykh
Dmitry Chestnykh
I think throwing an error is the right thing to do. That's how most of implementations behave. In my opinion, rounding up or down isn't the correct way to do...
I tried a prototype, but it turned out that currently it's not faster than the existing pure JS (nacl-fast) implementation. https://twitter.com/dchest/status/935099198583779328 I expect that a different, fully 64-bit X/Ed25519 implementation...
@evbogue not yet, sorry. I hope to work on it some time soon though.
@roopakv thank you! I’ll try to get some time to work on it this weekend.
This potentially breaks constant timing. Arrays created by `gf` must be able to contain at least 44 bits, which is why `Float64Array` is used (JavaScript numbers, which are double/float64 can...
Makes sense. Note that the [default import uses non-minefield version](https://github.com/dchest/tweetnacl-js/blob/f1ec050ceae0861f34280e62498b1d3ed9c350c6/package.json#L5), so unless the user of the library imports a minified file explicitly, nacl-fast.js will be used. I’ve marked this for...
*non-minified. But I like that autocorrect turned it into “non-minefield” 😄
To be fair, I would like to avoid exposing internals at all — they are mostly translated from the C code without proper JS conventions, and require a lot of...
I've decided that it wouldn't be wise to add WASM support to TweetNaCl, since proper C/Rust/Zig/etc libraries can be compiled and used instead of this one.
Do you know if adding `storage` permission will disable extension after update?