Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Problem: option key_backup_data_path means differently for command init and recover in sgx provider #54

Closed
allthatjazzleo opened this issue Apr 20, 2021 · 0 comments
Closed

Problem: option key_backup_data_path means differently for command init and recover in sgx provider #54

allthatjazzleo opened this issue Apr 20, 2021 · 0 comments

Comments

@allthatjazzleo
Copy link

Option key_backup_data_path in command::init refer to directory where consensus-key.backup will be created
while
Option key_backup_data_path in command::recover refer to the file path of consensus-key.backup

It could be confusing.

key_backup_data_path in command::recover should refer to directory as well?
allthatjazzleo added a commit to allthatjazzleo/tmkms-light that referenced this issue Apr 20, 2021
@allthatjazzleo
Problem: (fix crypto-com#54)option key_backup_data_path means differe…
59c0174 
…ntly for command init and recover in sgx provide

Solution: add consensus-key.backup to the key_backup_data_path
allthatjazzleo added a commit to allthatjazzleo/tmkms-light that referenced this issue Apr 20, 2021
@allthatjazzleo
Problem: (fix crypto-com#54)option key_backup_data_path means differe…
e7b51c2 
…ntly for command init and recover in sgx provide

Solution: add consensus-key.backup to the key_backup_data_path
@tomtau tomtau closed this as completed in a0138c8 Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@allthatjazzleo