Ranieri Althoff
Ranieri Althoff
I can reproduce it, but I could not isolate the root cause yet Edit: just found it. Seems to be related to Blake2 secure memory wipe from Argon2. Will try...
> This seems to be a problem that occurs when the version of Node.js is different between build and runtime. Interestingly, this seems to be only happening with Alpine. I...
Well, considering how much this hurts usability I think this goes the wrong way. One of our runtime dependencies, `node-addon-api` is a must so we can't drop that, but it...
> That was the main one that I didn't like and removed. Another possibility would be to switch to node-gyp and not provide pre-built binaries which I tried before and...
Is it still happening? The hashes are updated by yarn itself, and npm does not use yarn.lock, so these shouldn't interfere. > why add a SHA1 sum if there's a...
Yarn now changed everything to SHA512 again, and I guess this won't happen anymore.
There have been a couple of issues with Electron around here, most of them are environment issues and not specific to argon2. I can't provide much help as I personally...
Is it possible for you to require argon2 in the main thread, and pass it around to other threads? The whole intent of Argon2 is to be slow :stuck_out_tongue:
Hey! Sorry for the long wait. Can you check if the latest commit on master (0d9f0f8) fixes this issue? It fixes related issues with other packagers
In this case, you seem to be hitting the same issue of #261 which was resolved with this: https://github.com/ranisalt/node-argon2/issues/261#issuecomment-639392195