Chapter 38. Key management in OpenStack Security Guide - current

[N Dillon]

Providing encryption and key management services as part of OpenStack eases data-at-rest security adoption, addresses customer concerns about the privacy and misuse of their data with the added advantage of limiting cloud provider liability.

Run-on sentence, starts as a list 1) eases data-at-rest security adoption, 2) addresses customer concerns after "and" is continuation of #2.

Recommendation is to change command to 'and' and then change 'privacy and misuse' to 'privacy/misuse' to avoid confusion.
-----------------------------------
Built: 2014-07-15T06:45:42 00:00
git SHA: 46a1753b5222a021d2b75d5b97d3d4fac9804671
URL: http://docs.openstack.org/security-guide/content/key-management.html
source File: file:/home/jenkins/workspace/security-doc-tox-doc-publishdocs/security-guide/ch_key-management.xml
xml:id: key-management

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/108886

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/108886
Committed: https://git.openstack.org/cgit/openstack/security-doc/commit/?id=d9616871f6221524d8c311d8e8476b8299b0dc8e
Submitter: Jenkins
Branch: master

commit d9616871f6221524d8c311d8e8476b8299b0dc8e
Author: sicarie <email address hidden>
Date: Tue Jul 22 21:36:53 2014 -0700

    Broke out key mgmt run-on into more logical parts

    Changed ',' to 'and' grouping customer parts together
    Changed 'and' to 'or' to help not include in list
    Added comma and changed wording around provider liability

    Change-Id: I792d9e4980c00d90eefb822a1150fdb06e4bf244
    Closes-Bug: #1342279