Bug 1257292

Summary: [RFE][swift] At-Rest Encryption
Product: Red Hat OpenStack Reporter: Sean Cohen <scohen>
Component: openstack-swiftAssignee: Pete Zaitcev <zaitcev>
Status: CLOSED ERRATA QA Contact: Mike Abrams <mabrams>
Severity: medium Docs Contact:
Priority: high    
Version: unspecifiedCC: derekh, egafford, jschluet, nlevinki, pgrist, rhos-flags, sclewis, sgotliv, srevivo, thiago, zaitcev
Target Milestone: rcKeywords: FutureFeature, TechPreview, Triaged
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
URL: http://specs.openstack.org/openstack/swift-specs/specs/in_progress/at_rest_encryption.html
Whiteboard:
Fixed In Version: openstack-swift-2.9.1-0.20160726041039.25cdd52.el7ost Doc Type: Technology Preview
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-14 15:14:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 1386032    

Description Sean Cohen 2015-08-26 17:23:25 UTC
Currently objects are typically stored on disk as files in a standard POSIX filesystem.
When disks reach end-of-life, they are discarded, and if not properly wiped, may still contain data.
The feature provides option for Swift operators to have objects stored in an encrypted form.

Comment 4 Mike McCune 2016-03-28 23:46:50 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions

Comment 5 nlevinki 2016-05-16 07:26:52 UTC
Will be tested in Mitaka

Comment 8 Thiago da Silva 2016-07-05 14:04:21 UTC
This feature has been merged to upstream swift master: https://github.com/openstack/swift/commit/9045f338693474303f209a4909bca64031afbe9d

Comment 9 Elise Gafford 2016-10-05 11:52:42 UTC
Hi Pete,

Please set the NVR in fixed-in-build and set this to MODIFIED.

Comment 15 errata-xmlrpc 2016-12-14 15:14:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2948.html