You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Since version 1.13.0 we are unable to decrypt the pgp encrypted seal keys generated by Vault. This change seems to be the culprit: #16224
To Reproduce
Initialising vault with on the v1/sys/init endpoint with pgp keys configured returns keys_base64 which we cannot decrypt anymore.
echo "<key>" |base64 -d |gpg -dvvv
gpg: using character set 'utf-8'
# off=0 ctb=c1 tag=1 hlen=2 plen=94 new-ctb
:pubkey enc packet: version 3, algo 18, keyid 09F9C9B784CF56AE
data: [263 bits]
data: [392 bits]
gpg: public key is 0x09F9C9B784CF56AE
gpg: using subkey 0x09F9C9B784CF56AE instead of primary key 0xAF43259C18181A3F
gpg: pinentry launched (17986 gnome3 1.1.0 - xterm-256color :100)
# off=96 ctb=d2 tag=18 hlen=2 plen=113 new-ctb
:encrypted data packet:
length: 113
mdc_method: 2
gpg: using subkey 0x09F9C9B784CF56AE instead of primary key 0xAF43259C18181A3F
gpg: encrypted with 256-bit ECDH key, ID 0x09F9C9B784CF56AE, created 2024-03-15
"<my identity>"
gpg: public key decryption failed: Wrong secret key used
gpg: decryption failed: No secret key
Expected behavior
If i perform the exact same procedure on version 1.12.x
echo -n "<key>" |base64 -d|gpg -dvvv
gpg: using character set 'utf-8'
# off=0 ctb=c1 tag=1 hlen=2 plen=78 new-ctb
:pubkey enc packet: version 3, algo 18, keyid 09F9C9B784CF56AE
data: [263 bits]
data: [264 bits]
gpg: public key is 0x09F9C9B784CF56AE
gpg: using subkey 0x09F9C9B784CF56AE instead of primary key 0xAF43259C18181A3F
gpg: public key encrypted data: good DEK
# off=80 ctb=d2 tag=18 hlen=2 plen=0 partial new-ctb
:encrypted data packet:
length: unknown
mdc_method: 2
gpg: using subkey 0x09F9C9B784CF56AE instead of primary key 0xAF43259C18181A3F
gpg: encrypted with 256-bit ECDH key, ID 0x09F9C9B784CF56AE, created 2024-03-15
"<my identity>"
gpg: AES encrypted data
# off=101 ctb=cb tag=11 hlen=2 plen=0 partial new-ctb
:literal data packet:
mode t (74), created 0, name="",
raw data: unknown length
gpg: original file name=''
<unseal key>: decryption okay
Environment:
Working version 1.12.x
Failing versions: everything after
Describe the bug
Since version 1.13.0 we are unable to decrypt the pgp encrypted seal keys generated by Vault. This change seems to be the culprit: #16224
To Reproduce
Initialising vault with on the
v1/sys/init
endpoint with pgp keys configured returns keys_base64 which we cannot decrypt anymore.Expected behavior
If i perform the exact same procedure on version 1.12.x
Environment:
Working version 1.12.x
Failing versions: everything after
the deployment is on k8s with https://helm.releases.hashicorp.com/vault
The text was updated successfully, but these errors were encountered: