Hsmtool (and hsm_secret encryption) refactorings #4307
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.
This is a bunch of cleanups on top of #4303 .
Mainly, this makes the
hsm_encryption
contained into a common/ module, shared byhsmd
,lightningd
(options and hsm_control) andhsmtool
. This then allows us to fuzz a roundtrip sanity check of our encryption.Also:
hsmtool
encrypt
inhsmtool
hsm_secret
validity (only accept 32-bytes (plaintext) and 73-bytes (encrypted) seeds)There are still some cleanups left to be done (the channel seed derivation function is still duplicated, we could use
opt
for argument parsing).