I have a previously created cryptoloop filesystem (made under a different linux distro). Unfortunately it seems that losetup, or mount distributed with SuSE wont mount it because the password I used for the encrypted filesystem isnt at least 20 characters long. Every time I try, i get the following error: Error: Password must be at least 20 characters. Does anyone know a way to get around this? -- Grant Limberg GPG Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8C8E3D99
On Sun, 29 Aug 2004 13:23:59 -0700, Grant Limberg
I have a previously created cryptoloop filesystem (made under a different linux distro). Unfortunately it seems that losetup, or mount distributed with SuSE wont mount it because the password I used for the encrypted filesystem isnt at least 20 characters long. Every time I try, i get the following error:
Error: Password must be at least 20 characters.
Does anyone know a way to get around this?
Can anyone help on this issue? I can see needing that length of password for new encrypted loopback filesystems, and if I could, i'd reencrypt it with at least a 20 character password, but I cant even access the data right now! Any help would be much appriciated. Thanks -- Grant Limberg GPG Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8C8E3D99
The Sunday 2004-08-29 at 13:23 -0700, Grant Limberg wrote:
I have a previously created cryptoloop filesystem (made under a different linux distro). Unfortunately it seems that losetup, or mount distributed with SuSE wont mount it because the password I used for the encrypted filesystem isnt at least 20 characters long. Every time I try, i get the following error:
Error: Password must be at least 20 characters.
Does anyone know a way to get around this?
I also have an old encripted partition, but it was created under suse 8.1, I think. Suse 9.1 complains about the password, certainly, and also about the format, but it gets mounted anyway. I have it defined in '/etc/cryptotab', as: /dev/loop0 /dev/hdb7 /cripta reiserfs twofish defaults then, the script '/etc/init.d/boot.crypto start' mounts it during boot (or manually). In the fstab file, I have it as 'ignore': /dev/hdb7 /cripta ignore -- Cheers, Carlos Robinson
participants (2)
-
Carlos E. R.
-
Grant Limberg