Documentation lists the argument order of scrypt.paramsSync and
scrypt.params as maxtime, [maxmem, [max_memfrac]], and the argument
checking in index.js is consistent with this. However, both
src/node-boilerplate/inc/scrypt_params_async.h and
src/node-boilerplate/scrypt_params_sync.cc were accessing the arguments as
[maxtime, max_memfrac, maxmem], and thus returning incorrect results.
Documentation lists the argument order of
scrypt.paramsSyncandscrypt.paramsasmaxtime, [maxmem, [max_memfrac]], and the argument checking inindex.jsis consistent with this. However, bothsrc/node-boilerplate/inc/scrypt_params_async.handsrc/node-boilerplate/scrypt_params_sync.ccwere accessing the arguments as[maxtime, max_memfrac, maxmem], and thus returning incorrect results.