On Tue, Jun 27, 2017 at 9:40 AM, Trevor Perrin <tr...@trevp.net> wrote:

>  (B) A signing function that takes a user-specified private scalar
> (instead of Ed25519-style key derivation) to support extensions like
> XEdDSA where signing uses an existing X25519 private key; or Bitcoin's
> Hierarchical Deterministic key derivation.


This is a major shortcoming of the "bag of bytes" API provided by all
existing Ed25519 libraries to my knowledge, which always prehash the seed
value to generate the private scalar and nonce prefix, making it impossible
to provide your own scalar.

Would be wonderful to see it addressed by a more flexible/lower-level API
targeting more sophisticated protocols.

-- 
Tony Arcieri
_______________________________________________
Curves mailing list
Curves@moderncrypto.org
https://moderncrypto.org/mailman/listinfo/curves

Reply via email to