-
Notifications
You must be signed in to change notification settings - Fork 214
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix!: don't use the ledger unless both keys are for ledger (#6492)
Description --- Correct the key requests coming from the key manager in the Motivation and Context --- - Correct the `sign_with_nonce_and_challenge` code path to properly request ledger keys only when both keys are to be derived from the ledger, otherwise use the software key manage - Fix the tari script serialization on the metadata signature to produce proper sigs - Refactor the function to generate TariScripts on the ledger to be something a bit simpler - Refactor the metadata signature domain hashing. We were doing `hash(hash(script) + hash(common))` but this can be simplified to `hash(script + hash(common)`. There's no need to hash the script by itself, before hashing it alongside the common hash. How Has This Been Tested? --- One sided sends are borked from ledger. TX creation is requesting the wrong keys from ledger. Metadata signature generation is wrong. What process can a PR reviewer use to test or verify this change? --- Breaking Changes --- - [ ] None - [ ] Requires data directory on base node to be deleted - [x] Requires hard fork - [ ] Other - Please specify The change in hashing function causes the gen block, and faucets to no longer match. This hashing change is a breaking change for the purpose of simplification.
- Loading branch information
Showing
12 changed files
with
73 additions
and
112 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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 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 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 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 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 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 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 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 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 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 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