openstack/security-doc
Code Issues Proposed changes

change to section_data-privacy-concerns

Browse Source 
changed backend to back end for noun
backend should not be used according to doc standards
changed plugin to plug-in per conventions

Change-Id: I71f0478d847c4c704c1c8140d92d23f10cc3c844
This commit is contained in:
Shilla Saebi
2015-05-06 13:25:57 -04:00
parent 59fbcda57b
commit 661771cc47
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
security-guide/section_data-privacy-concerns.xml
View File

@@ -117,7 +117,7 @@
<para>Use of the OpenStack volume encryption feature is highly encouraged. This is
discussed in the Data Encryption section below. When this feature is used,
destruction of data is accomplished by securely deleting the encryption key.</para>
<para>If a backend plugin is being used, there may be independent ways of doing encryption or non-standard overwrite solutions. Plugins to OpenStack Block Storage will store data in a variety of ways. Many plug-ins are specific to a vendor or technology, whereas others are more DIY solutions around filesystems such as LVM or ZFS. Methods to securely destroy data will vary from one plugin to another, from one vendor's solution to another, and from one filesystem to another.</para>
<para>If a back end plug-in is being used, there may be independent ways of doing encryption or non-standard overwrite solutions. Plug-ins to OpenStack Block Storage will store data in a variety of ways. Many plug-ins are specific to a vendor or technology, whereas others are more DIY solutions around filesystems such as LVM or ZFS. Methods to securely destroy data will vary from one plug-in to another, from one vendor's solution to another, and from one filesystem to another.</para>
<para>Some back ends such as ZFS will support copy-on-write to
prevent data exposure. In these cases, reads from unwritten
blocks will always return zero. Other back ends such as LVM