Update libtomcrypt to 1.18.2 #673
Merged
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
required for sha256 usage
and remove a very very old hack that isnt needed
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.
Also adds a SHA256 method to CryptManager using LTC.
And at this point I realize we have picoSHA2 in our globals. So we could instead be removing all of LTC and move to use just that since I believe at this point most things in CryptManager are outdated/replaceable.
The motivation of this change was an update to chartkeys, which is why the decision to merge this might not be made until that change is taken seriously. The timing of this decision could be sooner rather than later.
Method of updating LTC directly inspired by stepmania/stepmania#1919