Bypass rand_hack to build for no_std #55
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
I am using schnorrkel signatures in a no_std environment, however the rand_hack requirement for signing via witness_scalar was causing collisions via rand_core. This PR introduces bypasses to calls to rand_hack and allows the caller to provide an rng. For example, with
default-features = false
, the following builds and runs in the no_std environment of SGX:This approach may also address related no_std issue #31.
In this PR
witness_scalar_rng
to SigningTranscriptsign_rng
to SecretKeysuper::rand_hack()