Skip to content
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

Call to undefined function Sodium\crypto_sign_ed25519_sk_to_curve25519() #48

Closed
ghost opened this issue Aug 23, 2017 · 4 comments
Closed

Comments

@ghost
Copy link

ghost commented Aug 23, 2017

Call to undefined function Sodium\crypto_sign_ed25519_sk_to_curve25519()

Isn't that covered ?

@paragonie-scott
Copy link
Member

It should be? Let me check, and if it's not, I'll make sure it lands in 1.2.0.

@ghost
Copy link
Author

ghost commented Aug 23, 2017

Actually, i did used libsodium now directly without sodium_compat.

sodium_crypto_sign_ed25519_sk_to_curve25519 - worked,

But i did also noticed that overall speed of execution is at least x5 faster without sodium_compat, why is that? why should i keep using sodium_compat and not directly libsodium via libsodium-php ?

@paragonie-scott
Copy link
Member

Well, sodium_compat is a polyfill. If you have the extension, you don't need it.

The purpose is so you can use the sodium features and, if someone for whatever reason doesn't have it installed, your code doesn't break. Sodium_compat is necessarily slower than the extension written in C.

@ghost
Copy link
Author

ghost commented Aug 23, 2017

Oh i see, i haven't researched it much. Good to know. I definitely see use case for that. Anyway, looking forward to crypto_sign_ed25519_sk_to_curve25519 && crypto_sign_ed25519_pk_to_curve25519.
I will mark this as resolved then.

@ghost ghost closed this as completed Aug 23, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant