You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Ledger application will often place a RistrettoSecretKey into a Zeroizing wrapper to ensure it is zeroized on drop. However, this is unnecessary, as the RistrettoSecretKey type already zeroizes on drop since it implementsSecretKey. All such wrappers can safely be removed for improved efficiency and clarity.
The text was updated successfully, but these errors were encountered:
Description
---
- Applied proper random nonces in the one-sided metadata signature to be
collision resistant.
- Removed double zeroizing on 'RistrettoSecretKey'.
- Ensured hasher output is zeroized.
- Changed Ledger BIP32 derivation to use 'secp256k1'.
Motivation and Context
---
See #6484, #6485, #6488 and #6490.
How Has This Been Tested?
---
System-level testing using a ledger device with `cargo run --release
--example ledger_demo`
What process can a PR reviewer use to test or verify this change?
---
- Code review
- `cargo run --release --example ledger_demo`
<!-- Checklist -->
<!-- 1. Is the title of your PR in the form that would make nice release
notes? The title, excluding the conventional commit
tag, will be included exactly as is in the CHANGELOG, so please think
about it carefully. -->
Breaking Changes
---
- [ ] None
- [ ] Requires data directory on base node to be deleted
- [ ] Requires hard fork
- [X] Other - Please specify
<!-- Does this include a breaking change? If so, include this line as a
footer -->
BREAKING CHANGE: All ledger derived keys and signatures will be
different.
The Ledger application will often place a
RistrettoSecretKey
into aZeroizing
wrapper to ensure it is zeroized on drop. However, this is unnecessary, as theRistrettoSecretKey
type already zeroizes on drop since it implementsSecretKey
. All such wrappers can safely be removed for improved efficiency and clarity.The text was updated successfully, but these errors were encountered: