3 ms·
> WARNING: This library DOES NOT WORK on 64-bit systems, and there's nothing I can do about it before the next version of NaCl is available. FWIW, that warning
by erichocean 14y ago
> WARNING: This library DOES NOT WORK on 64-bit systems, and there's nothing I can do about it before the next version of NaCl is available.
FWIW, that warning is...incorrect. Anyone who actually wants to use NaCl with Node.js (and we do) can trivially get a 64-bit build (it's even done through Python). I don't disagree that the original author of node-nacl wasn't skilled enough to do it though.
> There's also the elephant in the room: Windows. NaCl doesn't support Windows.
Say what? NaCl supports Windows just fine – it's just djb's 'do' build script that doesn't, along with how to get a random number. There's absolutely nothing to prevent anyone from using NaCl on Windows, if they are willing to integrate it into a normal Windows build system (which is...trivial) and make a few, trivial, API updates.
----
Having addressed those mis-understandings, Sodium is a welcome development and will certainly make it easier for people to develop bindings to NaCl.
- bascule 14y ago> Say what? NaCl supports Windows just fine – it's just djb's 'do' build script that doesn't, along with how to get a random number You realize you're describing exactly what Sodium fixes (portable build system + randombytes for Windows), right? That was my original point.
- deleted 14y ago[deleted]
- dsl 14y ago> FWIW, that warning is...incorrect. Or you have some fundamental flaw in your deployment now. Just because it compiles dosen't mean it's not vulnerable to say, a timing attack.