Revert "crypto: added runtime checks for SHA hardware" #3135
+52
−184
Conversation
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
This reverts commit e78cfc6. Besides adding runtime checks, this also removes experimental guards and makes the features leak into release code as we have no way of disabling them. Additionally, this breaks on non-gnu systems which currently have no released binaries, like arm-apple-darwin20 (Apple silicon macs)
|
I've compared this PR to me running |
chromatic
approved these changes
Oct 15, 2022
|
how can i do to make a money |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This reverts commit e78cfc6.
Besides adding runtime checks, this also removes experimental guards and makes the features leak into release code as we have no way of disabling them.
Additionally, this breaks on non-gnu systems which currently have no released binaries, like arm-apple-darwin20 (Apple silicon Macs)
To reproduce the issue on an M1:
Covers first item of solution proposed in #3134