On September 4, 2013 12:28:19 PM "Coffman, Joel M."
<joel.coff...@jhuapl.edu> wrote:
The following change provides a key manager implementation that reads a
static key from the project's configuration:
https://review.openstack.org/#/c/45103/
This key manager implementation naturally does not provide the same
confidentiality that would be proffered by retrieving keys from a service
like Barbican or a KMIP server, but it still provides protection against
certain attacks like intercepting iSCSI traffic between the compute and
storage host and lost / stolen disks.
I know this is meant as a minimalistic stub, but even so shouldn't it be
able to have at least a prior and current key?
How do you test a key management interface without changing keys?
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
