Change: Use checksum for proxy instead of weird flag#392
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Using checksum validation instead of weird flag.
Description
Currently bob is using a hack to validate whenever the proxy is using the latest version of bob, which works but eh, I hate it. Anyway this is using sha-2 in order to compare arrays of u8 checksum of the current running exe and the proxy.
Type of change
Checklist
Checklist tick-boxes
cargo fmtcargo clippy --all-targets -- -D warnings)or will be updated in a PR (Link here: )(if applicable)