From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] blobstore disk format (was Re: Design of the blobstore)
Date: Thu, 22 Sep 2011 09:37:44 +0300 [thread overview]
Message-ID: <20110922063744.GB29819@redhat.com> (raw)
In-Reply-To: <4E7A9305.909@linux.vnet.ibm.com>
On Wed, Sep 21, 2011 at 09:44:37PM -0400, Stefan Berger wrote:
> On 09/19/2011 03:04 PM, Michael S. Tsirkin wrote:
> >On Mon, Sep 19, 2011 at 12:22:02PM -0400, Stefan Berger wrote:
> >>On 09/17/2011 03:28 PM, Michael S. Tsirkin wrote:
> >>>On Fri, Sep 16, 2011 at 12:46:40PM -0400, Stefan Berger wrote:
> >>
> >>The checksuming I think makes sense if encryption is being added so
> >>decryption and testing for proper key material remains an NVRAM
> >>operation rather than a device operation.
> >Not sure how this addresses the question of what to do
> >on checksum failure.
> >
> Checksum failure on an unencrypted blob would mean that the blob is
> corrupted. In case of encryption 'corrupted' would overlap with a
> 'badly decrypted' blob. In either way the startup of the device
> cannot happen.
With corruption - why not? A specific block being corrupted does not mean all
data is lost.
> We could refuse the NVRAM key suggesting that likely
> this is the wrong key for decryption but corruption is also
> possible.
I'm guessing that if we find a correct ber structure in the file, this
most likely means the key is correct.
--
MST
next prev parent reply other threads:[~2011-09-22 6:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 12:28 [Qemu-devel] blobstore disk format (was Re: Design of the blobstore) Michael S. Tsirkin
2011-09-15 14:33 ` Stefan Berger
2011-09-16 14:44 ` Michael S. Tsirkin
2011-09-16 16:46 ` Stefan Berger
2011-09-17 19:28 ` Michael S. Tsirkin
2011-09-19 16:22 ` Stefan Berger
2011-09-19 19:04 ` Michael S. Tsirkin
2011-09-22 1:44 ` Stefan Berger
2011-09-22 6:37 ` Michael S. Tsirkin [this message]
2011-09-28 15:48 ` Stefan Berger
2011-09-28 15:50 ` Daniel P. Berrange
2011-09-28 19:19 ` Stefan Berger
2011-10-02 9:18 ` Michael S. Tsirkin
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=20110922063744.GB29819@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
/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).