All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: f000m@z1p.biz
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] GEOM_ELI support in dm-crypt/cryptsetup
Date: Sat, 30 Nov 2013 18:33:02 +0100	[thread overview]
Message-ID: <529A214E.1060305@gmail.com> (raw)
In-Reply-To: <be0befb7cada2ffce3a998455719664b@mail.secure-mail.biz>

Hi,

On 11/30/2013 04:25 PM, f000m@z1p.biz wrote:
> I am planing to make dm-crypt and cryptsetup able to
> handle FreeBSD's GEOM_ELI crypted devices (without its
> integrity stuff).

I think that even integrity stuff would be interesting
but that's a lot of kernel work.
(But I am quite interested how FreeBSD approach looks like anyway.)

> In the kernel modul there would be minor changes
> concerning two more IV generators needed to add:
> First, because of a slightly different handling of plain type
> (it uses offsets instead of sectors).
> Second, GEOM_ELI uses CBC with unpredictable IV instead of
> ESSIV Mode.

Not sure I understand offset/sectors problem.
Can you elaborate more here? Is it just multiplication
of sector number by sector size or something else?
(Or just point me to the docs :)

Anyway, adding new IV generators to dmcrypt should not be big problem
(in principle).

> Additionally cryptsetup must be patched to be able
> to deal with the metadata structure of GEOM_ELI devices.
> 
> Would there be any interests in committing me this code
> to the upstream?

Well, I am not sure how broadly this format is used and if
there are potential users in Linux world, so if you can
post more description here it would be nice.

(And if anyone on list is interested, plesase say so... now :)

But in general, yes, I think it is good idea.

I would suggest you to do these steps:

1) provide links to documentation of format, limitation
of your approach etc (also should be included in patch later)

2) first, implement needed changes in Linux kernel (dmcrypt IVs)
(if it is only new IV, it should be straightforward)
Please post patches to DM devel list (dm-devel@redhat.com)

This should be done in advance - for testing, you can use
dmsetup to configure dmcrypt device and test it works for your
images.

Cryptsetup support can come later (we need patch in stable kernel
first to release build supporting it).

3) second, post patches for cryptsetup to this list.

Please keep format specific code in separate directory,
lib/geli/* or so.
(I am planning some unified interface for formats in future (1.7),
so see how is e.g. TCRYPT done - it should be very similar).

Please post at least simple regression tests together with patches
(see tests/ dir).

License of new code must be compatible with released code,
basically GPL2+/LGPL2.1+ for cryptsetup.

(And be prepared it will take some time and perhaps reiterated
patch posts - mainly for kernel part :)

Thanks,
Milan

  reply	other threads:[~2013-11-30 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 15:25 [dm-crypt] GEOM_ELI support in dm-crypt/cryptsetup f000m
2013-11-30 17:33 ` Milan Broz [this message]
2013-12-13  6:42   ` f000m
2016-12-28 15:46     ` Carl-Daniel Hailfinger
2016-12-28 18:06       ` Carl-Daniel Hailfinger
2016-12-30  6:31         ` Carl-Daniel Hailfinger
2017-01-01 22:23           ` Milan Broz
2017-01-05  8:53             ` Carl-Daniel Hailfinger
2017-01-05 10:54               ` Carl-Daniel Hailfinger

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=529A214E.1060305@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=f000m@z1p.biz \
    /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.