Rationale for ecdh_skip_hash_extract_x_and_y
mikekelly opened this issue · 3 comments
This libarary is great, I really like the minimalist API but I'm having interoperability issues using it for ECDH.
I believe it is due to PrivateKey.sharedSecret using ecdh_skip_hash_extract_x_and_y
The result is Data that when put through SHA256.hash produces a inconsistent result from libraries like this:
I was wondering if this was an intentional design decision and what the rationale was?
👋 thanks a lot! Thanks for this, will investigate next week! Can't remember now why I did it like that. Can add parameter to swift function maybe? So the hash function can be chosen.
yeah, combined with an enum of the available functions (defaulting to .ecdh_skip_hash_extract_x_and_y, so the API doesn't break) would be a nice API :)
@mikekelly First of all, so so sorry for slowest response every! I was busy with other work. In #7 I've solved this issue, I now vendor three different ECDH variants, one of which is CryptoKit compatible, because it returns CryptoKit's SharedSecret struct which is really nice, since offers KDFs!
One which follows standards libsecp256k1 and lastly the old one (custom, no hash), please see the PR #7 for details.
I will make a new release 0.0.9 with these new APIs