2022-07-01 19:28:36 +00:00
|
|
|
Unseal Key 1: xb11HFT+6KBH0y8Jglvmr2ljnVIWZk9YruHLJpR4oVot
|
|
|
|
|
Unseal Key 2: aG8MUmlY0NbzHyIp5MSj98q7eCalUhrYmYXXMGozocSn
|
|
|
|
|
Unseal Key 3: 1BMKM86m6JMZL9DCypY1rbsfvuiO22Tm0i9E2T6a/UUU
|
|
|
|
|
Unseal Key 4: VZ36NLxKn/xC32TGDhThIPlndqSaXhmm3FFEewzoeAXk
|
|
|
|
|
Unseal Key 5: bAZ77ThRY6RfHM00q7kkSmknY0tqXla092PDPkuP5NfW
|
2021-10-12 19:36:06 +00:00
|
|
|
|
2022-07-01 19:28:36 +00:00
|
|
|
Initial Root Token: s.EQOap6R44K8Hpx3o7lB5ORqs
|
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.
|
