Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
None
-
None
Description
With HDDS-3612 buckets created via ozone are also accessible via S3.
This has caused a problem when the bucket is encrypted, the keys are not encrypted on disk.
2 Issues:
1. On OM, for each part a new encryption info is generated. During complete Multipart upload, the encryption info is not stored in KeyInfo.
2. On the client, for part upload, the encryption info is silently ignored.
If we don't throw an error, on an encrypted bucket, key data is not encrypted on disks.
For 0.6.0 release, we can mark this as not supported, and this will be fixed in next release by HDDS-4005
Attachments
Issue Links
- is a clone of
-
HDDS-4005 Support S3 MPU on encrypted buckets
- Resolved
- links to