Il 28/02/2014 23:08, Eric Blake ha scritto:
Use the fact that we are calling the next release "2.0" to actually kill qemu disk encryption as a horribly botched feature, on the grounds that we are doing users a favor by not letting them use broken encryption?
Only for qemu, of course---qemu-img would still have support for encryption, and there's no reason to risk stability by removing all the monitor code right now.
However, wouldn't we have the same problems even with a sane encrypted image format (based on LUKS, for example)?
Let's just open bugs (oh if only Launchpad supported tracker bugs) for now. Paolo
