Now that all encryption keys must be provided upfront via the QCryptoSecret API and associated block driver properties there is no need for any explicit encryption handling APIs in the block layer. Encryption can be handled transparently within the block driver. We only retain an API for querying whether an image is encrypted or not, since that is a potentially useful piece of metadata to report to the user. Reviewed-by: Alberto Garcia <berto@igalia.com> Reviewed-by: Max Reitz <mreitz@redhat.com> Signed-off-by: Daniel P. Berrange <berrange@redhat.com> Message-id: 20170623162419.26068-18-berrange@redhat.com Signed-off-by: Max Reitz <mreitz@redhat.com> |
||
---|---|---|
.. | ||
qmp | ||
clone-visitor.h | ||
dealloc-visitor.h | ||
error.h | ||
opts-visitor.h | ||
qmp-event.h | ||
qobject-input-visitor.h | ||
qobject-output-visitor.h | ||
string-input-visitor.h | ||
string-output-visitor.h | ||
util.h | ||
visitor-impl.h | ||
visitor.h |