Add nacl.sign.keyPair.fromSeed #37
Labels
Comments
dchest
added a commit
that referenced
this issue
Jul 27, 2014
Allows deriving a new sign key pair deterministically from a 32-byte seed. Introduces a tiny change to the low-level crypto_sign_keypair(): a new argument that indicates that sk already contains seed bytes; however crypto_sign_keypair() interface behaves exactly the same as before if this argument is not truthful (e.g. not set). Closes #37.
|
Discuss @ #46 |
dchest
added a commit
that referenced
this issue
Aug 3, 2014
Allows deriving a new sign key pair deterministically from a 32-byte seed. Introduces a tiny change to the low-level crypto_sign_keypair(): a new argument that indicates that sk already contains seed bytes; however crypto_sign_keypair() interface behaves exactly the same as before if this argument is not truthful (e.g. not set). Closes #37.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This function will return a key pair generated from a seed (which should be random), instead of calling
randombytesinternally, which is whatnacl.sign.keyPairdoes.On one hand, there's currently no way to do what this function does without copying half of the library, on the other hand, it complicates code (and makes diff from tweenacl.c not so pretty) for an uncommon use case (which can also be dangerous if you're not careful with producing proper seeds, e.g. from passwords with weak derivation function).
Filed under "maybe".
The text was updated successfully, but these errors were encountered: