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
{{ message }}
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.
To support legacy packer use with webkms, the internal cryptobox service must have remote capabilities to be run remotely on a key server.
Make CryptoBox a service and create a separate remote implementation and make legacy packer select the right implementation based on the kms implementation.
The text was updated successfully, but these errors were encountered:
Also fixes WithSender option in remoteCrypto's WrapKey/UnwrapKey
if the option is set without a sender key URL.
closeshyperledger-archives#2369
Signed-off-by: Baha Shaaban <baha.shaaban@securekey.com>
Also fixes WithSender option in remoteCrypto's WrapKey/UnwrapKey
if the option is set without a sender key URL.
closeshyperledger-archives#2369
Signed-off-by: Baha Shaaban <baha.shaaban@securekey.com>
sudeshrshetty
pushed a commit
to sudeshrshetty/aries-framework-go
that referenced
this issue
Jan 22, 2022
Also fixes WithSender option in remoteCrypto's WrapKey/UnwrapKey
if the option is set without a sender key URL.
closeshyperledger-archives#2369
Signed-off-by: Baha Shaaban <baha.shaaban@securekey.com>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To support legacy packer use with webkms, the internal cryptobox service must have remote capabilities to be run remotely on a key server.
Make CryptoBox a service and create a separate remote implementation and make legacy packer select the right implementation based on the kms implementation.
The text was updated successfully, but these errors were encountered: