All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoann CONGAL <yoann.congal@smile.fr>
To: dm-crypt@saout.de
Subject: [dm-crypt] LUKS container creation without device mapper or loop device access
Date: Fri, 18 Jun 2021 10:22:24 +0200	[thread overview]
Message-ID: <CAMSfU+5R5ZBeVjCkbeqRh33g_rJpZRrygs89zyf59s2Nb7QXrQ@mail.gmail.com> (raw)

Hi,

In some environments, we would like to build an image of a LUKS
container from a cleartext image of a filesystem without having access
to the device-mapper or a loop-device.

For context : this is often the case for building embedded linux
images with Yocto/Buildroot. These builds are more and more frequently
launched from containers (Docker, LXC, ...) and these do not have easy
access to the host kernel (for DM and loop).

From what I understood of the internals of cryptsetup, it knows how to
build the LUKS header but rely on the dm-crypt module of the kernel to
do the actual data encryption. (Please correct me if I'm wrong)

So, I have two questions :
* Do you know of a tool that does the full LUKS image (header and
data) fully in userland? (I did search for it and found nothing)
* If the above answer is "It does not exist yet", would you be open to
its inclusion in cryptsetup? My guess is that a tightly managed intern
may handle this.

Thanks!

Best regards,
-- 
Yoann Congal
Smile ECS - Expert technique
yoann.congal@smile.fr
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de

             reply	other threads:[~2021-06-18  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  8:22 Yoann CONGAL [this message]
2021-06-30  9:10 ` [dm-crypt] Re: LUKS container creation without device mapper or loop device access Ondrej Kozina
2021-07-01 15:57   ` Yoann CONGAL

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=CAMSfU+5R5ZBeVjCkbeqRh33g_rJpZRrygs89zyf59s2Nb7QXrQ@mail.gmail.com \
    --to=yoann.congal@smile.fr \
    --cc=dm-crypt@saout.de \
    /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.