Cinder creating and associating symmetric keys with encrypted volumes when used with Barbican

Bug #1693840 reported by Lee Yarwood
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned

Bug Description

Description
===========

Cinder is creating and associating symmetric keys with encrypted volumes when used with Barbican. As discussed on the dev ML [1] these symmetric keys are not used to directly encrypt or decrypt these volumes within Cinder or Nova (via os-brick).

It would be less confusing to users and operators if passphrases were instead stored in Barbican and associated with these encrypted volumes. While Barbican does currently allow for secret passphrases to be stored the associated key manager interface provided by Catellan and used by Cinder and Nova does not. This will need to be extend before any changes can be made to Cinder.

[1] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117467.html

Lee Yarwood (lyarwood)
summary: - Cinder is creating and associating symmetric keys with encrypted volumes
+ Cinder creating and associating symmetric keys with encrypted volumes
when used with Barbican
Revision history for this message
Kaitlin Farr (kaitlin-farr) wrote :

Castellan does allow for passphrases to be stored.

https://github.com/openstack/castellan/blob/master/castellan/common/objects/passphrase.py

You would need to create a Passphrase object and use the key_manager.store() command to store it. However, you'd need to either get the user to input the passphrase or randomly generate the bytes somewhere. Generating symmetric/asymmetric keys is a standard key manager feature, but generating passphrases is not.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.