Package: cryptsetup
Version: 2:1.0.6-6
Severity: wishlist

I) Right now we have on case (AFAIK) where no keyscripts are used:
When "none" is specified in crypttab and only a password is used as key

II) If bug #509072 will be fixed, we'd miss our current "passdev-keyscript"

III) If bug #509071 will be fixed, we'd neet tries support for this "none"-case.

How to solve all of this?

I'd suggest the following:
1) For every decryption (even in the "none"-case") a keyscript is used.
2) Create a new keyscript which implements tries, and uses/supports passdev and uses just askpass for password reading, but nothing else like (gpg or ssl or whatever).

That way we'd solve II and III (for I we don't have to solve anything XD) and even add fancy usplash/splashy support for the "none"-case via askpass support for those.


Chris.

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cryptsetup depends on:
ii dmsetup 2:1.02.27-4 The Linux Kernel Device Mapper use
ii  libc6                        2.7-16      GNU C Library: Shared libraries
ii libdevmapper1.02.1 2:1.02.27-4 The Linux Kernel Device Mapper use ii libpopt0 1.14-4 lib for parsing cmdline parameters
ii  libuuid1                     1.41.3-1    universally unique id library

cryptsetup recommends no packages.

Versions of packages cryptsetup suggests:
ii  dosfstools                    3.0.1-1    utilities for making and checking
ii  initramfs-tools [linux-initra 0.92m      tools for generating an initramfs
ii udev 0.125-7 /dev/ and hotplug management daemo

-- no debconf information


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.




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

Reply via email to