Bug#373973: rewrite cryptdisks as a wrapper around cryptsetup

[David Härdeman]

I will try to implement a preliminary version sometime next week (or the
week after depending on how much time it takes).

Currently I plan to implement it as a C program which uses the
libvolume_id and devmapper libraries (which removes the need to use vol_id
from udev).

Jonas, is it ok if I create a new directory in the cryptsetup SVN repo for
development of this program?

Re,
David



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#373973: rewrite cryptdisks as a wrapper around cryptsetup

[Jonas Meurer]

On 22/06/2006 David Härdeman wrote:
 I will try to implement a preliminary version sometime next week (or the
 week after depending on how much time it takes).
 
 Currently I plan to implement it as a C program which uses the
 libvolume_id and devmapper libraries (which removes the need to use vol_id
 from udev).

sounds like a great plan!

 Jonas, is it ok if I create a new directory in the cryptsetup SVN repo for
 development of this program?

sure, go ahead.

...
 jonas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#373973: rewrite cryptdisks as a wrapper around cryptsetup

[Jonas Meurer]

Package: cryptsetup
Version: 2:1.0.3-2
Severity: wishlist

cryptdisks should be a wrapper around cryptdisks, comparable to mount.
basicly it should do the same as the current cryptdisks initscript,
except that it can be invoked from the commandline.

* David Härdeman wrote:
 Usage examples:

 o mount all crypt-disks
 cryptmount -a

 o setup crypt-disk named croot (defined in /etc/crypttab)
 cryptmount croot

 o list all known cryptdisks
 cryptmount -l

 Then cryptmount (or whatever we call it) can contain all the code for
 parsing /etc/crypttab. This should help with the current early/late
 init.d scripts as they both simply call cryptmount -a and also means that
 I can include the wrapper in the initramfs image, thereby reducing those
 scripts quite a lot.

cryptmount/cryptdisks should support dynamical devices which are not
configured in /etc/crypttab as well. the syntax could look like:

o setup plain crypt-disk named cusb (not defined in /etc/crypttab)
cryptmount /dev/sdf4 cusb
o setup luks crypt-disk named cstick (not defined in /etc/crypttab)
cryptmount /dev/sde1 cstick -o luks,key=/etc/keys/cstick,timeout=5

ideally the wrapper should be written in C, to make it faster than the
current bash shell script.

...
 jonas

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-rc3-1-amd64-resivo
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages cryptsetup depends on:
ii  dmsetup  2:1.02.07-1 The Linux Kernel Device Mapper use
ii  libc62.3.6-15GNU C Library: Shared libraries
ii  libdevmapper1.02 2:1.02.07-1 The Linux Kernel Device Mapper use
ii  libgcrypt11  1.2.2-1 LGPL Crypto library - runtime libr
ii  libgpg-error01.2-1   library for common error values an
ii  libpopt0 1.10-2  lib for parsing cmdline parameters
ii  libuuid1 1.39-1  universally unique id library

cryptsetup recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]