-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Newly added functions lack version checks #83
Comments
damn. sorry. fixing it right now. |
hmmmm. looks like there are some constants that have been only added in 1.0.12 but the crypto_pwhash_scryptsalsa208sha256 interface existed previously already since at least 1.0.8. dunno what the best course is, remove the sanity checks entirely for that interface, or enable them only if libsodium is >=1.0.12, and let the previous versions fly blindly? |
please confirm the fix of this bug by b38db7d by closing this issue. |
I found one more instance, see #84 .
Another option would be to hardcode the values of those constants in 1.0.8...<1.0.12. |
ah, the hardcoding thing seems like the right solution to this problem, i'll do that! thanks for the insight! keep this ticket open until i commit that fix. |
…on_checks, and some reordering of the consts
i hardcoded the missing values in case they do not exist, also i removed the sodium_version_checks which are made obsolete by this (and i reordered some of the constants to make them more human friendly) in 1d00f0c. |
Some of the constants/functions added in bca3999 do not exist in earlier versions of libsodium, like the one I have from Ubuntu 16.04, which is version 1.0.8. I get an error like:
I don't have time to figure out each of them at the moment or I would have tried to make a PR.
The text was updated successfully, but these errors were encountered: