Define an tag specifying volume encryption format and
format-depenedent parameters (e.g. passphrase, cipher name, key
length, key).
In most cases, the "secrets" (passphrases/keys) should only be
transferred from libvirt users to libvirt, not the other way around.
(Volume creation, when libvirt ge
On Tue, Jul 21, 2009 at 01:11:57PM +0200, Miloslav Trma?? wrote:
> Define an tag specifying volume encryption format and
> format-depenedent parameters (e.g. passphrase, cipher name, key
> length, key).
>
> In most cases, the "secrets" (passphrases/keys) should only be
> transferred from libvirt
- "Daniel P. Berrange" wrote:
> On Tue, Jul 21, 2009 at 01:11:57PM +0200, Miloslav Trma?? wrote:
> > +#include
> > +#include
> > +
> > +enum virStorageEncryptionFormat {
> > +VIR_STORAGE_ENCRYPTION_FORMAT_UNENCRYPTED = 0,
> > +VIR_STORAGE_ENCRYPTION_FORMAT_QCOW, /* Both qcow and qcow
On Fri, Jul 24, 2009 at 12:08:32AM -0400, Miloslav Trmac wrote:
> - "Daniel P. Berrange" wrote:
> > On Tue, Jul 21, 2009 at 01:11:57PM +0200, Miloslav Trma?? wrote:
> > > +#include
> > > +#include
> > > +
> > > +enum virStorageEncryptionFormat {
> > > +VIR_STORAGE_ENCRYPTION_FORMAT_UNENC
- "Daniel P. Berrange" wrote:
> For the domain XML I agree that libirt would not need to worry about
> multiple LUKS keys, but for the storage volume XML we would need to
> expose the fact that there are multiple keys,or allow creation of
> volumes with multiple keys.
I don't know. Does a f
