2023-02-22 14:16:27 +00:00
|
|
|
Unseal Key 1: rDjUVcpsiwv3SDmAAavfkMBJ2O2H9XfsmMXOXaI46zT0
|
|
|
|
|
Unseal Key 2: ww7AgnhYINM7BpD1v2LHyBsPn10CWT2AnPm5KfCN48Ve
|
|
|
|
|
Unseal Key 3: jH5WxSmY0I+InM0W4n4L9H9jKXW1BLPGFLCMfVTF8tFb
|
|
|
|
|
Unseal Key 4: qfxj3ejTGD1tawonOjXRG+qdIFNZHSsRJIUqp6x2PLHw
|
|
|
|
|
Unseal Key 5: HGT+smfQdbGKQsHa+Aci1x3u2RPjNQZHJ8ouUPNXPpvC
|
2021-10-12 19:36:06 +00:00
|
|
|
|
2023-02-22 14:16:27 +00:00
|
|
|
Initial Root Token: hvs.iLynNrOHmG74IT29P6zMnShH
|
2021-10-12 19:36:06 +00:00
|
|
|
|
|
|
|
|
Vault initialized with 5 key shares and a key threshold of 3. Please securely
|
|
|
|
|
distribute the key shares printed above. When the Vault is re-sealed,
|
|
|
|
|
restarted, or stopped, you must supply at least 3 of these keys to unseal it
|
|
|
|
|
before it can start servicing requests.
|
|
|
|
|
|
|
|
|
|
Vault does not store the generated master key. Without at least 3 key to
|
|
|
|
|
reconstruct the master key, Vault will remain permanently sealed!
|
|
|
|
|
|
|
|
|
|
It is possible to generate new unseal keys, provided you have a quorum of
|
|
|
|
|
existing unseal keys shares. See "vault operator rekey" for more information.
|
