3 ms·
The easiest way to get round the slightly odd build environment for NaCl is to just use TweetNaCl (http://tweetnacl.cr.yp.to/software.html http://tweetnacl.cr.y
by _paulc 12y ago
The easiest way to get round the slightly odd build environment for NaCl is to just use TweetNaCl (http://tweetnacl.cr.yp.to/software.html http://tweetnacl.cr.yp.to/software.html) which just requires you to drop a single .c/.h file into your project - this isn't as performant as the reference code but in most cases this probably doesn't matter. The libsodium implementation seems overly complicated to me for most uses.
The NaCl API is reasonably simple and is fairly easy to wrap (plug - if anyone is looking for an example have a look at jim-nacl [1] which embeds into Jim TCL)
[1] https://github.com/paulchakravarti/jim-nacl https://github.com/paulchakravarti/jim-nacl
- urras 12y agoMight also want to checkout libsodium (https://github.com/jedisct1/libsodium https://github.com/jedisct1/libsodium).
- _paulc 12y agoExcept that this is the opposite of my point - the libsodium repository is 9MB with 326 .c/.h files and c.25000 lines of code. Tweetnacl is 2 .c/.h files and c.1000 lines of code.