[Pkg-cryptsetup-devel] Bug#408976: cryptsetup: --key-file=- produces different mapper device than --key-file=<keyfile>

[Goran Gmitrovic]

Package: cryptsetup
Version: 2:1.0.4+svn26-1
Severity: normal

Using one of the previous verions of "/usr/share/initramfs-tools/scripts/local-top/cryptroot" together with the option "keyscript" in "/etc/crypttab" 
worked fine for me until you add "--key-file=-" to this line 198 "$cryptkeyscript $cryptkey < /dev/console | $cryptcreate --key-file=-". 

My keyscript was
ROOTKEY="$1"
/bin/cat $ROOTKEY | /bin/sha1sum 
The output was then hashed by cryptsetup. So I changed the last line to 
/bin/cat $ROOTKEY | /bin/sha1sum | /sbin/hashalot -n 32 sha256
to produce now the raw keyfile information. However, it did not work. 
 
Should "--key-file=-" really be used to get the raw keyfile information from the stdin, because "cryptsetup --key-file=- create <name> <device>" asks for 
the passphrase?


Many thanks

Regards
GG


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages cryptsetup depends on:
ii  dmsetup  2:1.02.08-1                     The Linux Kernel Device Mapper use
ii  libc6    2.3.6.ds1-8                     GNU C Library: Shared libraries
ii  libdevma 2:1.02.08-1                     The Linux Kernel Device Mapper use
ii  libgcryp 1.2.3-2                         LGPL Crypto library - runtime libr
ii  libgpg-e 1.4-1                           library for common error values an
ii  libpopt0 1.10-3                          lib for parsing cmdline parameters
ii  libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-1 universally unique id library

cryptsetup recommends no packages.

-- no debconf information