openstack
/
barbican-specs
Code Issues Proposed changes

Modify grammatical errors 

Change-Id: I8d1ed77f83fb9620127c77fdc87514fe38ead4de
This commit is contained in:
melissaml 2018-02-08 00:44:24 +08:00
parent fc2ef0eafc
commit e4d20d581b
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/juno/add-certificate-to-the-container-type.rst
View File

@ -27,7 +27,7 @@ not be distinguishable.
Proposed Change
===============
Add the `certificate` option for containers. This augments the the current type attribute on the containers resource and data model to accept `certificate` as a valid option.
Add the `certificate` option for containers. This augments the current type attribute on the containers resource and data model to accept `certificate` as a valid option.
Alternatives
------------

2
specs/kilo/add-creator-only-option.rst
View File

@ -14,7 +14,7 @@ Problem Description
-------------------
This is a companion spec to the add-per-secret-policy spec. That spec proposed
a mechanism for allowing users outside the the secrets project to access a
a mechanism for allowing users outside the secrets project to access a
secret/container. This mechanism involved storing access control data
in the database for each secret/container.

2
specs/kilo/barbican-mkek-model.rst
View File

@ -91,7 +91,7 @@ provide its reference to the MKEK as the wrapping key so the HSM may unwrap it.
An unwrapped DEK, provided by the project, will be sent to the HSM and then
retrieved, wrapped by the projects KEK. This wrapped DEK will be stored in the
local Barbican database. The unwrapped DEK and KEK will now be removed from the
HSM. This logic will placed within the the encrypt() interface method.
HSM. This logic will placed within the encrypt() interface method.
Project Data Encryption Key (DEK) retrieval.
A project wrapped DEK (its encrypted secret) will be retrieved from Barbican's