Bug 1472465 - rgw multisite: objects encrypted with SSE-KMS do not sync correctly
rgw multisite: objects encrypted with SSE-KMS do not sync correctly
Status: ASSIGNED
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RGW (Show other bugs)
2.3
Unspecified Unspecified
medium Severity high
: rc
: 3.0
Assigned To: Casey Bodley
ceph-qe-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-18 15:58 EDT by Casey Bodley
Modified: 2017-08-08 11:00 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Ceph Project Bug Tracker 20671 None None None 2017-07-18 15:58 EDT

  None (edit)
Description Casey Bodley 2017-07-18 15:58:19 EDT
Description of problem:

Objects encrypted with the SSE-KMS mode sync to other zones, but are stored in their unencrypted form. Because they retain their encryption attributes, attempts to read them from a secondary zone will decrypt the data again, returning garbage data to the client.


How reproducible:

All objects encrypted with SSE-KMS in a multisite configuration.


Steps to Reproduce:
1. Set up a multisite configuration with two zones, including these additional values in ceph.conf:
[client]
  rgw crypt require ssl = false
  rgw crypt s3 kms encryption keys = testkey=YmluCmJvb3N0CmJvb3N0LWJ1aWxkCmNlcGguY29uZgo=

2. Create a bucket on the primary zone
3. Upload an object (containing readable text) to that bucket on the primary zone, using these additional request headers:
  x-amz-server-side-encryption: aws:kms
  x-amz-server-side-encryption-aws-kms-key-id: testkey

Actual results:

The object syncs to the secondary zone, but its data does not match the readable text uploaded to the primary zone.

Expected results:

The synced object is stored on the secondary zone in its encrypted form. When read, the decrypted object data is returned to the client.

Additional info:

The sync request should fetch the object in its encrypted form.

Note You need to log in before you can comment on or make changes to this bug.