2023-06-19 13:45:13 +00:00
|
|
|
Unseal Key 1: BXyPvDeMDzfzarrN2Gmtl0YBuCuhrSllhYindRR2Sdle
|
|
|
|
Unseal Key 2: EhN9f3J1+FdawXsApoUNT3MlSMTk7zCBBWteuYj6azgf
|
|
|
|
Unseal Key 3: XGTCoW5eMSykc+Gn1A01gTtM2wxpIi9i5hTydFni+AQJ
|
|
|
|
Unseal Key 4: NcfyD1ORFugYg8wt7AXvEFpNlMUiPrxjDoRR359UbD8Y
|
|
|
|
Unseal Key 5: UJMEzTKKVpNMtlhTDzOzwesBfI/Yfo5pfAViHnDvtZ3D
|
2021-10-12 19:36:06 +00:00
|
|
|
|
2023-06-19 13:45:13 +00:00
|
|
|
Initial Root Token: hvs.tyA2bCvimuDETIFyeDw2rqU5
|
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.
|