From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Nate Bushman <Nate.Bushman@storagecraft.com>,
Kai Meyer <kai.meyer@storagecraft.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Add support for new image type
Date: Fri, 09 Mar 2012 12:26:42 +0100 [thread overview]
Message-ID: <4F59E8F2.2060106@redhat.com> (raw)
In-Reply-To: <4F59DB5A.1020809@redhat.com>
Am 09.03.2012 11:28, schrieb Paolo Bonzini:
> Il 09/03/2012 10:23, Kevin Wolf ha scritto:
>>> You make really good points on opening up the image file format.
>>> I see real value there in that it would foster development of
>>> other solutions around that format. The problem in this case is
>>> that StorageCraft's backup image format uses proprietary
>>> compression and encryption, and so, regrettably, we can't
>>> (currently) open up that code.
>>
>> This is an interesting statement. Not so much for compression, for
>> which I can't know how much better your solution is than common
>> algorithms. But I always thought that closed encryption algorithms
>> have to be considered bad, because using them would mean relying on
>> security by obscurity. Which probably everyone agrees is a bad idea.
>
> And even for compression, having an open decompressor is usually a good
> idea. Some people have no problems with proprietary solutions but do
> not like lock in (and wonder what to do with their backups if
> StorageCraft disappears).
The lock-in you already get with uncompressed images, but yes, it's a
problem with this file format that would make me avoid it.
Kevin
next prev parent reply other threads:[~2012-03-09 11:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 21:52 [Qemu-devel] Add support for new image type Kai Meyer
2012-03-01 0:16 ` Brian Jackson
2012-03-01 15:03 ` Kevin Wolf
2012-03-01 19:45 ` Kai Meyer
2012-03-01 20:10 ` Stefan Weil
2012-03-01 20:18 ` Stefan Weil
2012-03-01 20:31 ` Kai Meyer
2012-03-01 21:05 ` Anthony Liguori
2012-03-01 21:14 ` Kai Meyer
2012-03-02 6:54 ` Paolo Bonzini
2012-03-02 18:38 ` Kai Meyer
2012-03-05 9:14 ` Paolo Bonzini
2012-03-05 12:14 ` Stefan Hajnoczi
2012-05-16 17:06 ` Kai Meyer
2012-05-16 17:48 ` Paolo Bonzini
2012-05-16 18:21 ` Anthony Liguori
2012-05-16 18:56 ` Kai Meyer
2012-05-16 19:20 ` Kai Meyer
2012-05-17 9:10 ` Artyom Tarasenko
2012-05-17 9:41 ` Paolo Bonzini
2012-05-17 11:03 ` Artyom Tarasenko
2012-05-17 17:53 ` Kai Meyer
2012-05-17 19:43 ` Paolo Bonzini
2012-05-17 20:18 ` Kai Meyer
2012-03-01 20:26 ` Kai Meyer
2012-03-01 20:38 ` Paolo Bonzini
2012-03-01 20:53 ` Stefan Weil
2012-03-01 21:02 ` Anthony Liguori
2012-03-08 15:17 ` Kevin Wolf
2012-03-08 17:16 ` Nate Bushman
2012-03-09 9:23 ` Kevin Wolf
2012-03-09 10:28 ` Paolo Bonzini
2012-03-09 11:26 ` Kevin Wolf [this message]
2012-03-10 16:54 ` Nate Bushman
2012-03-10 16:53 ` Nate Bushman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F59E8F2.2060106@redhat.com \
--to=kwolf@redhat.com \
--cc=Nate.Bushman@storagecraft.com \
--cc=kai.meyer@storagecraft.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).