Project

General

Profile

Feature #41670

rgw: crypt: permit RGW-AUTO/default with SSE-S3 headers

Added by Matt Benjamin almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus, mimic, luminous
Reviewed:
Affected Versions:
Pull request ID:

Description

Permit the existing logic for encrypton by a global master key
to take effect when a client has requested AES256 server-side encryption
with S3 managed keys, as well as SSE-KMS.

The official intent that rgw_crypt_default_encryption_key be for testing only is unchanged.


Related issues

Copied to rgw - Backport #43012: nautilus: rgw: crypt: permit RGW-AUTO/default with SSE-S3 headers Resolved
Copied to rgw - Backport #43013: luminous: rgw: crypt: permit RGW-AUTO/default with SSE-S3 headers Resolved
Copied to rgw - Backport #43014: mimic: rgw: crypt: permit RGW-AUTO/default with SSE-S3 headers Resolved

History

#1 Updated by Nathan Cutler over 1 year ago

  • Status changed from Fix Under Review to Pending Backport

#2 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #43012: nautilus: rgw: crypt: permit RGW-AUTO/default with SSE-S3 headers added

#3 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #43013: luminous: rgw: crypt: permit RGW-AUTO/default with SSE-S3 headers added

#4 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #43014: mimic: rgw: crypt: permit RGW-AUTO/default with SSE-S3 headers added

#5 Updated by Nathan Cutler over 1 year ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF