We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It's fairly typical for storage systems to provide an encrypt at REST to ensure both the key's data + channel are encrypted.
I don't think you can store encoded keys.
The text was updated successfully, but these errors were encountered:
Is this similar to #7250? The idea is to wrap the client KV and Txn implementations to encrypt data going into etcd and decrypt it coming out.
Sorry, something went wrong.
yup.. I'll close this one in favor for that one.
No branches or pull requests
It's fairly typical for storage systems to provide an encrypt at REST to ensure both the key's data + channel are encrypted.
I don't think you can store encoded keys.
The text was updated successfully, but these errors were encountered: