Comment 1 for bug 363229

hey martin,

this bug is not reproducible with recent cryptsetup (1.0.7). actually it's the other way round:

# dd if=/dev/urandom of=testkey1 bs=1 count=512
512+0 records in
512+0 records out
512 bytes (512 B) copied, 0.00259551 s, 197 kB/s
# gpg -o testkey1.gpg -r test --encrypt testkey1
# cryptsetup luksFormat /dev/vg_int/ctest_key testkey1
Command successful.
# cryptsetup --key-file=testkey1 luksOpen /dev/vg_int/ctest_key ctest_key
key slot 0 unlocked.
Command successful.
# cryptsetup luksClose ctest_key

# gpg -q --decrypt testkey1.gpg | cryptsetup --key-file=- luksOpen /dev/vg_int/ctest_key ctest_key

You need a passphrase to unlock the secret key for
user: "test test (test) <email address hidden>"
2048-bit ELG-E key, ID F3927D08, created 2009-09-01 (main key ID 3D18A229)

key slot 0 unlocked.
Command successful.
# cryptsetup luksClose ctest_key

# gpg -q --decrypt testkey1.gpg | cryptsetup luksOpen /dev/vg_int/ctest_key ctest_key

You need a passphrase to unlock the secret key for
user: "test test (test) <email address hidden>"
2048-bit ELG-E key, ID F3927D08, created 2009-09-01 (main key ID 3D18A229)

Command failed: No key available with this passphrase.

i suggest you to re-encrypt the keyfile with gnupg. which cryptsetup version do you use?

greetings,
 jonas