Dick Middleton schrieb:
....
losetup /dev/loop5 ~/.secret
cryptsetup luksFormat /dev/loop5
cryptsetup luksOpen /dev/loop5 ~/.secret
Why last parameter ~/.secret ????
Sorry, that is because I transscribed the commands per hand instead of
cut and paste. I did enter it correctly on my computer.
I just repeated the test. Transscript is below, this time by cut & paste
:-) . luksOpen hangs. No go after the last line.
Then I even tried a second time (different file, different
loopback-device). This time luksFormat went dead.
Then the same script on SuSE 10.0. Result: "key slot 0 unlocked.Command
successful."
If this is some bug I will be happy to help find it. I just don't know
where to look for the cause.
Stefan
----------------------------------------------------------------------------------
suse-st:~ # dd if=/dev/urandom of=~/.secret bs=1M count=4
4+0 records in
4+0 records out
4194304 bytes (4.2 MB) copied, 2.42336 seconds, 1.7 MB/s
suse-st:~ # losetup /dev/loop5 ~/.secret
suse-st:~ # cryptsetup luksFormat /dev/loop5
WARNING!
========
This will overwrite data on /dev/loop5 irrevocably.
Are you sure? (Type uppercase yes): YES
Enter LUKS passphrase:
suse-st:~ # cryptsetup luksOpen /dev/loop5 .secret
Enter LUKS passphrase:
###### HANG forever ... ######
----------------------------------------------------------------------------------
---------------------------------------------------------------------
- http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx
