Base64 encoding doesn't work in Safari's web workers about tweetnacl-js

[alax]

@mdp React Native doesn't use Webkit, it just uses JavaScriptCore, which is a wrapper around Webkit's Javascript engine. That also means that you won't have secure random number generator, so unless you've implemented one yourself, TweetNacl won't even work under React Native.

[dchest]

For everyone's information, this was recently fixed in WebKit https://bugs.webkit.org/show_bug.cgi?id=158576

[anri-asaturov]

http://code.google.com/p/gflot/source/browse/trunk/flot/base64.js?r=153 can solve this

[mdp]

This also happens React Native for iOS since it's using a webkit engine that doesn't support atob and doesn't have Buffer

[dchest]

@mdp thanks for letting me know!

I think I'll deprecate the nacl.utils part sometime in the future. As explained in docs:

Encoding/decoding functions are provided for convenience. They are correct, however their performance and wide compatibility with uncommon runtimes is not something that is considered important compared to the simplicity and size of implementation. You can use third-party libraries if you need to.

[mdp]

@dchest Yeah that's fair, I just wanted to add to this thread in case anyone else runs across it.

@alax Thanks, this is really good to know. I was only using it for decryption, but it's something I'll definitely keep in mind.

[alax]

@mdp Ahh, gotcha. Yeah, you are right, decryption would be 100% fine.

[dchest]

@alax @mdp yep, only key generation needs random numbers: secretbox, cryptobox, signing all work fine without PRNG if you already have keys, as mentioned here.