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

registry node init subcommand assumes file signer #3011

Closed
kostko opened this issue Jun 14, 2020 · 0 comments · Fixed by #3012
Closed

registry node init subcommand assumes file signer #3011

kostko opened this issue Jun 14, 2020 · 0 comments · Fixed by #3012
Assignees
@kostko
Labels
c:bug Category: bug c:cli Category: command line interface

Comments

@kostko
Copy link
Member

kostko commented Jun 14, 2020

The registry node init subcommand assumes a file signer factory is used for node identity signers and specifying any other signer (e.g., composite, remote, etc.) only has an effect for the entity signer (which is not even used most of the time as entity-signed descriptors are a debug-only feature).
@kostko kostko added c:bug Category: bug c:cli Category: command line interface labels Jun 14, 2020
@kostko kostko mentioned this issue Jun 15, 2020
Merged
@kostko kostko self-assigned this Jun 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kostko kostko

Labels
c:bug Category: bug c:cli Category: command line interface
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

go/oasis-node: Support non-file signers in registry node init oasisprotocol/oasis-core
1 participant
@kostko