openstack
/
horizon
Code Issues Proposed changes

Fix aes-xts key length in Horizon Admin Guide / Manage Volumes 

When using aes-xts-plain64, a 512 bit key produces an error as this
is not a supported barbican key length for aes-xts-plain64. This patch
updates the horzion admin doc to remove the reference of a 512 bit key.

Change-Id: Ie36e05a1e59eb88b779c9f3249a714c20b5f5fe0
Closes-Bug: #1708505
Closes-Bug: #1849196
This commit is contained in:
Keith Berger 2019-10-21 16:20:51 -04:00 committed by KeithMnemonic
parent ab12da098c
commit 85a1dddf12
1 changed files with 3 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/admin/manage-volumes.rst
View File

@ -101,14 +101,9 @@ volumes.
| | |type 'cryptsetup benchmark' |
| | |for additional options |
+--------------------+-----------------------+----------------------------+
| Key Size (bits)| 512 (Recommended for |Using this selection for |
| | aes-xts-plain64. 256 |aes-xts, the underlying key |
| | should be used for |size would only be 256-bits*|
| | aes-cbc-essiv) | |
+ +-----------------------+----------------------------+
| | 256 |Using this selection for |
| | |aes-xts, the underlying key |
| | |size would only be 128-bits*|
| Key Size (bits)| 256 (Recommended for |Using this selection for |
| | aes-xts-plain64 and |aes-xts, the underlying key |
| | aes-cbc-essiv) |size would only be 128-bits*|
+--------------------+-----------------------+----------------------------+
`*` Source `NIST SP 800-38E <https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38e.pdf>`_