An implementation of a key manager that reads its key from the project’s configuration options.
This key manager implementation provides limited security, assuming that the key remains secret. Using the volume encryption feature as an example, encryption provides protection against a lost or stolen disk, assuming that the configuration file that contains the key is not stored on the disk. Encryption also protects the confidentiality of data as it is transmitted via iSCSI from the compute host to the storage host (again assuming that an attacker who intercepts the data does not know the secret key).
Because this implementation uses a single, fixed key, it proffers no protection once that key is compromised. In particular, different volumes encrypted with a key provided by this key manager actually share the same encryption key so any volume can be decrypted once the fixed key is known.
Bases: cinder.keymgr.key_mgr.KeyManager
Key Manager that supports one key defined by the fixed_key conf option.
This key manager implementation supports all the methods specified by the key manager interface. This implementation creates a single key in response to all invocations of create_key. Side effects (e.g., raising exceptions) for each method are handled as specified by the key manager interface.
Creates a key.
This implementation returns a UUID for the created key. A NotAuthorized exception is raised if the specified context is None.
Retrieves the key identified by the specified id.
This implementation returns the key that is associated with the specified UUID. A NotAuthorized exception is raised if the specified context is None; a KeyError is raised if the UUID is invalid.
Stores (i.e., registers) a key with the key manager.