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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Update cryptography tools to support
tssEncryptionKey
loading and generation #16780base: develop
Are you sure you want to change the base?
feat: Update cryptography tools to support
tssEncryptionKey
loading and generation #16780Changes from all commits
9acf000
6fe3072
bd19e1a
79edcb1
da91b85
59cd3bc
1d5bd12
186b839
1d91d3f
105fd61
3d7c771
232c5c0
899eef1
c3ee862
bc63214
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 645 in platform-sdk/swirlds-platform-core/src/main/java/com/swirlds/platform/crypto/CryptoStatic.java
Codecov / codecov/patch
platform-sdk/swirlds-platform-core/src/main/java/com/swirlds/platform/crypto/CryptoStatic.java#L644-L645
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to fail catastrophically by throwing an exception? Or can we return null and let the private key be regenerated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes we could return null and let the private key be regenerated.
However, this behavior should be clear in the node operator documentation. In the case of the private key becoming corrupted on-disk, it would be regenerated and a new public key submitted without giving the operator a chance to restore the private key from a backup.
Check warning on line 411 in platform-sdk/swirlds-platform-core/src/main/java/com/swirlds/platform/crypto/EnhancedKeyStoreLoader.java
Codecov / codecov/patch
platform-sdk/swirlds-platform-core/src/main/java/com/swirlds/platform/crypto/EnhancedKeyStoreLoader.java#L409-L411
Check warning on line 478 in platform-sdk/swirlds-platform-core/src/main/java/com/swirlds/platform/crypto/EnhancedKeyStoreLoader.java
Codecov / codecov/patch
platform-sdk/swirlds-platform-core/src/main/java/com/swirlds/platform/crypto/EnhancedKeyStoreLoader.java#L477-L478
Check warning on line 483 in platform-sdk/swirlds-platform-core/src/main/java/com/swirlds/platform/crypto/EnhancedKeyStoreLoader.java
Codecov / codecov/patch
platform-sdk/swirlds-platform-core/src/main/java/com/swirlds/platform/crypto/EnhancedKeyStoreLoader.java#L482-L483
Check warning on line 120 in platform-sdk/swirlds-platform-core/src/main/java/com/swirlds/platform/crypto/KeysAndCerts.java
Codecov / codecov/patch
platform-sdk/swirlds-platform-core/src/main/java/com/swirlds/platform/crypto/KeysAndCerts.java#L120