Hi Got a question. I just installed loop-aes here to try it, since I only have an older loop version installed And I fear that I cannot reproduce it when the system ever crashes. I am trying to figure out, how to get loop-aes to read the old partitions (which are on DVD - some as container some just as raw data). I have already installed the ciphers since I need twofish-256 for it. The original loop only asks for password, not keysize (which is given as -e twofish-256) and it uses no gpg-keyfile or therelike. If all goes wrong, I can always get the data down from all DVDs with my old system and copy it to a new system (either loop-aes or windows "DriveCrypt" which is my encryption for my workplace), but I'd like to avoid this. It seems, that cryptography on linux is somewhat complicated with all the different patched versions of "losetup" and "mount" around - not to mention the various kernel-patches... So if loop-aes is not compatible to my old files, I might try 4GB drivecrypt-containerfiles to burn on DVD for now until I can be sure that my crypto-files will still be accessible in some years... Is there no encryption avaiable that will be readable and writeable with windows and linux? Ciao A.W. -----Ursprungliche Nachricht----- Von: linux-crypto-bounce@xxxxxxxxxxxx [mailto:linux-crypto-bounce@xxxxxxxxxxxx]Im Auftrag von Jari Ruusu Gesendet: Sonntag, 24. April 2005 18:47 An: Peter_22@xxxxxx Cc: linux-crypto@xxxxxxxxxxxx Betreff: Re: SuSE 9.3 64-Bit and problems with booting from usb-stick Peter_22@xxxxxx wrote: > > Please post your compressed kernel config and build-initrd.sh config. > > Both are attached as .gz files. Build-initrd.sh config looked ok. Didn't look at kernel config because /lib mount appears to be ok. > Command "/lib/loadkeys /lib/default.kmap" returned error > Command "/lib/insmod /lib/modules-2.6.11.4-20a-default/loop.ko" returned > error Error message "Mounting /dev/sdb1 as /lib failed" means that /lib mount failed. Above error messages mean that /lib was already mounted successfully, but there is some userspace library dependence that causes the failure. Plan A ~~~~~~ Make sure that all programs copied to your USB-stick have their libraries copied there also. As in 'ldd /sbin/losetup ; ldd /sbin/insmod' and so on. At least Red Hat and Gentoo seem to ship ldd program that no longer outputs proper path to the library file in all cases, and that causes build-initrd.sh script to skip those libraries. I would not be surprised if SUSE had adopted that same braindamage as well. Plan B ~~~~~~ Can you try setting INITRDONLY=1 in build-initrd.sh config and manually copy statically linked copies off all needed programs (losetup, insmod, loadkeys and gpg) to your USB-stick. -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
