BIP32: Disambiguate Which Key Is Compromised When Ext. PubKey + PrivKey Are Leaked #64
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
…Leaked I mistakenly inferred from the following clause that a parent extended public key plus a child private key would be equivalent to knowing the extended *child* private key---meaning that the *parent* private key was still secure: > knowledge of the extended public key + any non-hardened private key > descending from it is equivalent to knowing the extended private key This patch's addition of the word "parent" (twice) removes the ambiguity and may help other readers draw the correct inference that the parent private key is no longer secure in this case. I also changed "+" to "plus" to avoid confusion with the actual mathematical operations used in this BIP.
|
I just took a look at other issues with BIPs---which I should've done first (sorry)---and discovered that #62 mentions the same issue. |
|
As author of BIP32, @sipa can you comment on this change? |
|
ACK |
laanwj
added a commit
that referenced
this pull request
Oct 15, 2014
BIP32: Disambiguate Which Key Is Compromised When Ext. PubKey + PrivKey Are Leaked
jachiang
pushed a commit
to jachiang/bips
that referenced
this pull request
Sep 16, 2019
Add a footnote about 32-byte security
real-or-random
pushed a commit
to real-or-random/bips
that referenced
this pull request
Feb 23, 2023
Make naming of nonce variants R in mediawiki and code consistent
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.
I mistakenly inferred from the following clause that a parent extended public key plus a child private key would be equivalent to knowing the extended child private key---meaning that the parent private key was still secure:
This patch's addition of the word "parent" (twice) removes the ambiguity and may help other readers draw the correct inference that the parent private key is no longer secure in this case.
I also changed "+" to "plus" to avoid confusion with the actual mathematical operations used in this BIP.