DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nathaniel McCallum <npmccallum@redhat.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] [ANNOUNCE] LUKSMeta
Date: Fri, 13 May 2016 12:01:06 -0400	[thread overview]
Message-ID: <1463155266.2542.14.camel@redhat.com> (raw)

https://github.com/latchset/luksmeta

Hi everyone! Several projects that I am working on or related to
require the ability to store some small metadata that is accessable
before the LUKS volume is unlocked. Since this was not possible with
LUKSv1, and we couldn't wait until LUKSv2, we created a small library
called LUKSMeta.

This simple library allows an application developer to store some
metadata in the gap in the LUKSv1 header (between the end of the
keyslots and the start of the payloadOffset). There are up to eight
"slots" of metadata, similar to the eight keyslots of LUKS. Each slot
is typed by a 16-byte UUID, so that applications don't stomp on each
others' data. Both the LUKSMeta header and the data in each slot is
checksummed (CRC32c) to detect data corruption.

There are four simple functions:

* luksmeta_init() - Write the LUKSMeta header to disk
* luksmeta_get() - Read data/uuid from a LUKSMeta slot
* luksmeta_set() - Write data/uuid to a LUKSMeta slot
* luksmeta_del() - Clear (zero) a LUKSMeta slot

More detailed documentation is available in the header:
https://github.com/latchset/luksmeta/blob/master/luksmeta.h

I have not made the first release, but I would like to do so soon. I
welcome your review/feedback. Thanks!

Nathaniel

             reply	other threads:[~2016-05-13 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 16:01 Nathaniel McCallum [this message]
2016-05-13 16:23 ` [dm-crypt] [ANNOUNCE] LUKSMeta Arno Wagner
2016-05-13 17:53   ` Nathaniel McCallum
2016-05-15 17:33     ` Milan Broz

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=1463155266.2542.14.camel@redhat.com \
    --to=npmccallum@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox