stn21 wrote:
Hi,
please excuse just in case this has been discussed before. I have just
signed up :-)
cryptsetup 1.0.3 works fine on SuSE 10.0 (Eval) but on SuSE 10.1 it
hangs for no apparent reason.
I have tested this on 2 different PCs with SuSE 10.1.
What I wanted to do is mount a loopback-volume:
dd if=/dev/urandom of=~/.secret bs=1M count=4
losetup /dev/loop5 ~/.secret
cryptsetup luksFormat /dev/loop5
cryptsetup luksOpen /dev/loop5 ~/.secret
Why last parameter ~/.secret ????
luksOpen <device> <name>
opens the LUKS partition <device> and sets up a mapping
<name> after successful verification of the supplied key
material (either via key file by --key-file, or via
prompting). <options> can be [--key-file, --readonly].
It should just be an identifier like "secret". You ultimately get a
device: /dev/mapper/secret
Dick
---------------------------------------------------------------------
- http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx
