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
At present all the KMS structs ( SecretKMS,AWSMetadataKMS...etc) where EncryptDEK(), DecryptDEK, ..etc methods are implemented are exposed. However considering all KMS structs reside in the same package (ie kms) we may not need to expose this struct,
This issue track the revalidation and once confirmed all the KMS structs can be unexported.
Ex:
// SecretsKMS is default KMS implementation that means no KMS is in use.
type SecretsKMS struct {
IntegratedDEK
passphrase string
}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.
Describe the bug
At present all the KMS structs ( SecretKMS,AWSMetadataKMS...etc) where EncryptDEK(), DecryptDEK, ..etc methods are implemented are exposed. However considering all KMS structs reside in the same package (ie kms) we may not need to expose this struct,
This issue track the revalidation and once confirmed all the KMS structs can be unexported.
Ex:
Additional Ref# #2723 (comment)
Cc @nixpanic
The text was updated successfully, but these errors were encountered: