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.

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

Change init to not blow away existing keys (if exist) #368

Closed
jstuczyn opened this issue Oct 8, 2020 · 1 comment · Fixed by #386
Closed

Change init to not blow away existing keys (if exist) #368

jstuczyn opened this issue Oct 8, 2020 · 1 comment · Fixed by #386
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@jstuczyn
Copy link
Contributor

jstuczyn commented Oct 8, 2020

Instead introduce extra init flag like --purge-existing-keys that would force fresh keygen.

@jstuczyn jstuczyn added the enhancement New feature or request label Oct 8, 2020
@jstuczyn jstuczyn added this to the 0.9.0 milestone Oct 8, 2020
@jstuczyn jstuczyn added this to Backlog in Core systems via automation Oct 8, 2020
@futurechimp
Copy link
Contributor

Thinking about this a bit more, I would even say we should never provide the option to use init to delete keys. We should just force users to rm their existing keys manually so that we know they really really mean it. Simpler for us and nobody ever uses the nym-client to destroy their valuable keys (that's a DIY operation).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Core systems
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants