You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understand it correctly, the essential logic (class ScryptEncoder) was created with commit f68083b on 2014-11-14.
After that (if I look at the individual commits) only a few minor changes were made to the actual algorithm.
I am now wondering what version of the tarsnap reference implementation this project corresponds to?
On the tarsnap scrypt website you can see that version 1.1.6 was still the latest in 2014.
Did you then transfer any relevant changes from the reference implementation to Scrypt.NET, @viniciuschiele ?
How is it ensured that potentially still open errors that are fixed in the reference algorithm are also fixed in Scrypt.NET?
The latest tarsnap version (published in october 2023) is 1.3.2. How do you keep up with it?
These questions may sound a little less friendly than they are meant to be 😉 I really appreciate your work. I'm just considering using Scrypt.NET, so I'm interested in these points.
The text was updated successfully, but these errors were encountered:
If I understand it correctly, the essential logic (class
ScryptEncoder
) was created with commit f68083b on 2014-11-14.After that (if I look at the individual commits) only a few minor changes were made to the actual algorithm.
I am now wondering what version of the tarsnap reference implementation this project corresponds to?
On the tarsnap scrypt website you can see that version 1.1.6 was still the latest in 2014.
Did you then transfer any relevant changes from the reference implementation to Scrypt.NET, @viniciuschiele ?
How is it ensured that potentially still open errors that are fixed in the reference algorithm are also fixed in Scrypt.NET?
The latest tarsnap version (published in october 2023) is 1.3.2. How do you keep up with it?
These questions may sound a little less friendly than they are meant to be 😉 I really appreciate your work. I'm just considering using Scrypt.NET, so I'm interested in these points.
The text was updated successfully, but these errors were encountered: