-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
rekey panic with pgp-keys
defined but not set
#7485
Labels
Milestone
Comments
It's actually not key-shares=0 that is the problem, it's the empty list at the end of pgp-keys. |
-key-shares=0
pgp-keys
defined but not set
@chrishoffman Hello, can I take this issue? I'm new in Go, but this issue is pretty clear for me. |
aivinog1
added a commit
to aivinog1/vault
that referenced
this issue
Sep 27, 2019
gedigi
added a commit
to gedigi/vault
that referenced
this issue
Oct 2, 2019
chrishoffman
pushed a commit
that referenced
this issue
Oct 9, 2019
Fixed by #7526 |
chrishoffman
pushed a commit
that referenced
this issue
Oct 9, 2019
chrishoffman
added a commit
that referenced
this issue
Oct 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
index out of range when rekeying with zero keys
To Reproduce
Steps to reproduce the behavior:
vault operator init -key-threshold=1 -key-shares=1
vault operator rekey -init -key-threshold=2 -key-shares=0 -pgp-keys=
Expected behavior
An error explaining that
-key-shares=0
makes no senseEnvironment:
vault status
): 1.1.3vault version
): Vault v1.1.3 ('9bc820f700f83a7c4bcab54c5323735a581b34eb')Vault server configuration file(s):
The text was updated successfully, but these errors were encountered: