-
Notifications
You must be signed in to change notification settings - Fork 5
Not expected hash #6
Comments
On certain android devices (have had this with an s8 for example) for unknown reasons libscrypt gives us wrong results. @demetris-manikas had tried to figure this out with the authors of libscrypt unsuccessfully iirc. |
Can confirm that emulator is working fine... My suggestion would be to put a warning on README for the time being - s8 is quite a popular phone. I will try to figure out. |
The truth is that the problem was solved by using code from another source. Details here. technion/libscrypt#39 |
Feel free to fix, I have no time to dig into this at the moment but can test and will accept a PR. |
@ggozad There is a branch in this project called FEAT-tarsnap which I believe you already have tested that solves the problem exactly as discussed in technion/libscrypt#39. Feel free to retest! |
Have you tried to run it with phonegap? Because this never runs second alert:
It simply does not call success nor error callback in emulator. Will try plain cordova later. |
Your code has a mistake. In the success callback "key" is not defined so change it to "res" and report back. Thanks |
Sorry, my original code had no mistake and test was wrong. Anyway it still not working:
|
And just tested same sequence with "cordova" instead of phonegap and it worked. I can easily switch to cordova but i wonder why phonegap is failing. I have no idea how to debug this one. |
I've merged FEAT-tarsnap and added plugin from my repo |
Hey, I've been sick the last few days :( Tomorrow I should be good to go to the office again and will look further into this. I need to review the changes on tarsnap but it seems the issue was the |
Fixed in 2.1.1 |
hex returned is not equal one from node's scrypt or scrypt-async-js libs, for default or any other opts https://gist.github.com/homakov/a3d9ae0a2d83b45e25cc297030dd5522
Is there any example that would return same value for the above libraries and for this plugin? I simply pass password/salt as bare strings UTF8 encoded
The text was updated successfully, but these errors were encountered: