All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Samantha Adams <saman.adams@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Use of GCM mode with dm-crypt
Date: Wed, 27 Apr 2011 11:41:01 +0200	[thread overview]
Message-ID: <4DB7E4AD.3030906@redhat.com> (raw)
In-Reply-To: <BANLkTi=YPXeJ92anQgCHi7rjfJNfsRM+Vw@mail.gmail.com>

On 04/27/2011 10:40 AM, Samantha Adams wrote:
> I would like to continue the post from December 2010 concerning GCM
> as it seems to be one of the few available modes to provide data
> integrity.
> 
> It is true that GCM adds the authenication tag in every sector and as
> result we are going to have a sector bigger in size. So, it makes it
> unsuitable for use with dmcrypt.

Exactly. dmcrypt provides just transparent encryption so the ciphertext
device and plaintext device is of the same size, we have no space
to store authentication tag to.

> But is it possible to allocate some space elsewhere for the tag ? Are
> they any possible modifications we could make so we could use gcm
> with dmcrypt ?

Basically it would be new encryption DM target (it can share code
but the mapping here is different).

The crucial question where do you want to store authentication tag...
If there is some standard way, perhaphs it can be done.

But isn't better to provide these integrity services to filesystem
on top of dmcrypt? (so fs can allocate blocks storing integrity info)

Milan

  reply	other threads:[~2011-04-27  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  8:40 [dm-crypt] Use of GCM mode with dm-crypt Samantha Adams
2011-04-27  9:41 ` Milan Broz [this message]
2011-04-27 13:43   ` Arno Wagner
2011-05-03 12:22     ` Samantha Adams
2011-05-03 12:46       ` Will Drewry

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=4DB7E4AD.3030906@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=saman.adams@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.