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

Deterministic signing #26

Closed
celil-kj opened this issue Jun 6, 2014 · 2 comments
Closed

Deterministic signing #26

celil-kj opened this issue Jun 6, 2014 · 2 comments

Comments

@celil-kj
Copy link

celil-kj commented Jun 6, 2014

Does signing a messge using secp256k1_ecdsa_sign in this library require a random number generator? Are there any plans to implement RFC 6979 which describes a scheme that would make the signing process completeley determinisitc? That would make the library useful for signing messages on embedded systems where there isn't sufficient entropy such as the recently released trezor.

@sipa
Copy link
Contributor

sipa commented Jun 12, 2014

You pass the signing secret nonce in as a parameter. You can either generate it randomly (which requires a good RNG), or you can use RFC 6979 yourself to come up with it. The current API is just too low-level to say it implements or doesn't implement it - it depends on how you use it.

I do plan on implementing a slightly higher level API, where you pass in function pointers for generating randomness, and hashing. In that setting, we could have natively implemented RFC 6979.

@sipa
Copy link
Contributor

sipa commented Jun 15, 2014

This is probably a part of #4.

@sipa sipa closed this as completed Jun 15, 2014
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

2 participants