Add Naver Cloud Wrapper #6
Conversation
Signed-off-by: jsmoon <[email protected]>
jsmoon-openerd
changed the title
jsmoon-openerd
force-pushed
the
ncloud
branch
3 times, most recently
from
883cb22 to
027bfbb
Compare
|
Wow @jsmoon-openerd! This looks fairly comprehensive on first glance. I'll have to take more time this weekend to review the PR. Thank you! I am a little worried about the size of go-kms-wrapping, what's your thoughts on eventually splitting it into a plugin architecture? If we make go-kms-wrapping v3 be PKCS#11 only, we can take the existing providers and turn them into PKCS#11 client libraries (especially where ones don't exist already)... Thoughts? |
|
Hey @jsmoon-openerd, do you mind splitting this into three PRs, one for each new backend? Thanks in advance! |
jsmoon-openerd
changed the title
|
\o hello @jsmoon-openerd -- as discussed on yesterday's community call, we're going to hold off on these three PRs until after GA, to continue letting GA stabilize before then. Thanks for your understanding and patience. :-) |
Add KMIP, Naver Cloud, PKCS#11 Wrapper
The KMIP wrapper has been tested with PyKMIP.
KMIP currently support AES encryption algorithm.
PKCS#11 currently support RSA, AES encryption algorithm.
openbao/openbao#300