Results 1 to 1 of 1
Greetings
After a long wait I finally had the 9.1 in my hands and made a clean install.
Beforehand I copied my /home to an encrypted loopback hd. Installation went ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 06-11-2004 #1Just Joined!
- Join Date
- Jun 2004
- Posts
- 1
suse 9.1 professional and encryptions made with suse 9.0
Greetings
After a long wait I finally had the 9.1 in my hands and made a clean install.
Beforehand I copied my /home to an encrypted loopback hd. Installation went fine but for some reason I can't seem to mount the loopback hd anymore.
Here some of my logs:
beta@linux:~> su
Password:
linux:/home/beta # /etc/rc.d/boot.crypto start
Activating crypto devices using /etc/cryptotab ...
Please enter passphrase for /dev/hdc2. Switching to old S.u.S.E. loop_fish2 compatibility mode.
Password:
WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
Passwords shorter than 20 characters are considered too short and insecure.
Use of rmd160 password hash permits use of such short passwords for
compatibility with other systems that do not enforce minimum length.
Hopefully this message is annoying enough that you discontinue using such
short passwords.
WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
An error occured. Maybe the wrong passphrase was
entered or the file system on /dev/hdc2 is corrupted.
losetup:
linux:/home/beta # losetup -a
/dev/loop0: [0302]:27914 (/dev/hdc2)
dmesg:
loop: registered Twofish encryption
ReiserFS: loop0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on loop0
cryptotab:
/dev/loop0 /dev/hdc2 /home/250 reiserfs twofish noatime
So is there an incompatability issue with encryption made with a 2.4 kernel or have just fsked something up along the way while trying to recover the hd?
Any assistance would be greatly appreciated.[/code]


Reply With Quote
