DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jürgen Pabel" <jpabel@akkaya.de>
To: dm-crypt@saout.de
Subject: [dm-crypt] Shared library for cryptsetup
Date: Thu, 24 Sep 2009 21:44:55 +0200	[thread overview]
Message-ID: <1253821495.4683.25.camel@P7230> (raw)

Hi all,

I would like to see the shared library included in the next release (ie:
establishing a somewhat stable API+ABI). I know this has been focused on
in the past and some work has already been done - but: I would really
like to see this to be an official part of a release in the near future.

Why? My project "tokentube" is an integration component between LUKS and
credential verification via PAM on Linux. It allows for users to use
their Linux username and password to unlock LUKS during system startup
(instead of a dedicated encryption passphrase). There's a presenation
online in case you want to know more about tokentube:

http://programm.froscon.org/2009/attachments/93_From%20PBA%20To%
20Login.pdf

It would be great if I could employ a custom binary to do the
initialization (which includes adding a new key to LUKS) instead of
calling the cryptsetup binary from configuration scripts.

Regards,
Jürgen

-- 
Jürgen Pabel, CISSP

Akkaya Consulting GmbH
Eupener Straße 137
50933 Köln

Telefon: +49 221 9473007
Telefax: +49 221 4911970
Mobil:   +49 160 8806133

E-Mail:   jpabel@akkaya.de
Internet: http://www.akkaya.de

             reply	other threads:[~2009-09-24 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 19:44 Jürgen Pabel [this message]
2009-09-25 13:02 ` [dm-crypt] Shared library for cryptsetup Milan Broz
2009-09-29 11:44 ` Ludwig Nussel
2009-10-11 23:17   ` Jürgen Pabel
2009-10-12  9:12     ` Ludwig Nussel
2009-10-12 12:53       ` Heinz Diehl

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=1253821495.4683.25.camel@P7230 \
    --to=jpabel@akkaya.de \
    --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