fix: updates for SafePassword
API change
#4927
Merged
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.
Description
Minor updates for a corresponding change to the
SafePassword
API.Motivation and Context
A pending change in
tari_utilities
to the handling of sensitive data includes a new implementation ofSafePassword
. One change removes derived traits for equality testing in favor of equality testing on references to the underlying passphrase data. This work makes the minor but necessary changes to address this API change.How Has This Been Tested?
Tests pass after applying the linked
tari_utilities
PR. Note that tests will pass using the currentSafePassword
API as well, as the dependency change PR restricts the API.