You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Looks like a good addition. In the general case, we can point people towards our RustCrypto fork for 100% compatibility. There was no test to run the RsaCompat so I added one in 2e48ada. (Although I suppose the failure was at build time anyway)
Update: with a moment of thought, I reverted that commit and added a comment instead. e71c957
Is there any advantage to using risc0_zkp::core::hash::sha::rust_crypto::Sha256 as opposed to the patched RustCrypto fork? One option is to just drop this entire rust_crypto.rs to make it less confusing for folks. Could we have risc0-zkvm rely on the patched fork also?
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.
@dobbobalina2 Here's my attempt to get
Pkcs1v15Sign
to work with the sha2 accelerator.