Code

Programming Languages: C

License: GNU General Public License version 2.0 (GPLv2)

Show:

What's happening?

  • Boot CD with Loop-AES support

    I've just been told that with respect to GRML, "AFAIK loop-aes is deprecated and you should switch sooner rather than later to dm-crypt or luks". This follows the removal of Loop-AES from Knoppix some time ago. It seems as though I need to resume my quest for a boot CD that supports Loop-AES. This could be a bit of opensource politics, however, is Loop-AES deprecated?...

    2012-03-06 17:57:52 PST by fog_watch

  • Comment: loop-aes fails to build on kernel 3.2, Debian wheezy

    Thanks for the hint, it was solved by installing full sources (don't know if they are needed) and running: make MODINST=n LINUX_SOURCE=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux-headers-3.2.0-1-686-pae/ Winfried.

    2012-02-21 06:05:54 PST by nobody

  • Comment: loop-aes fails to build on kernel 3.2, Debian wheezy

    Please re-read loop-AES README section 3, first two paragraphs. Looking at your error messages and loop-AES source, your case looks like kernel source headers are not in a state that can be used to compile loop-AES (or other) kernel modules. Specifically, LINUX_VERSION_CODE from linux/version.h is missing or it indicates wrong kernel version.

    2012-02-18 23:25:28 PST by jariruusu

  • loop-aes fails to build on kernel 3.2, Debian wheezy

    Hi, First of all thanks a lot for loop-aes. I have been using it for many years and I still can't do without. Then the problem I encounter: I try to build the loop-aes kernel modules for a 3.2 kernel on Debian wheezy. I use the debian pacage linux-headers-3.2.0-1-686-pae (3.2.4-1), loop-aes v3.6e as downloaded from sourceforge and DKMS. The build log says: DKMS make.log for...

    2012-02-18 00:38:48 PST by nobody

  • Comment: Slow write performance on Debian squeeze

    > Will this still be an issue? Internal linux kernel interfaces change. loop-AES-v3.3a version will most likely fail to compile for that linux-3.2 kernel. Latest loop-AES should compile and work OK with that earlier mentioned lo_prealloc=4096 parameter tuning. Guys, If you post as "nobody", please include some sort of nickname in your post. I'm having difficulties...

    2012-02-08 06:51:19 PST by jariruusu

  • Comment: Slow write performance on Debian squeeze

    Current stable loop-AES source package in Debian Squeeze is version 3.3a-1 http://packages.debian.org/squeeze/loop-aes-source uname -r gives 3.2.0-1-486 Will this still be an issue?.

    2012-02-07 08:07:54 PST by nobody

  • Comment: Full Disk Encryption - loop on /dev/sda

    > additional loops based on offsets into the first loop Additional loops backed by /dev/sda. Two loops stacked is wasted resources. Only first loop device (the one that is set up by initrd) needs a passphrase, other loop devices can read cleartext key file from encrypted+mounted root file system. /dev/loop0 -> /dev/sda sectors 0...999 /dev/loop1 -> /dev/sda sectors...

    2012-01-28 23:11:57 PST by jariruusu

  • Comment: Full Disk Encryption - loop on /dev/sda

    Thank you for the great reply! Sorry about the previous comment. I had not yet read your response. You have already answered my previous questions. > Disadvantage of full device use for root file system is that you can't use some of the same disk as swap (encrypted or not). What about a swap file? That seems like it should work. > build-initrd.sh initrd + LVM combination requires...

    2012-01-28 13:31:38 PST by jmasinter

  • Comment: Full Disk Encryption - loop on /dev/sda

    I have read some more and understand that when you loop on the raw device, that you must make additional loops based on offsets into the first loop, to create artificial partitions. I am getting closer now. The question remains, in the current rev of tools, is there an offset limit of 2G? That would be impractical for current day disk sizes and partitioning. If so, is there a patch to extend...

    2012-01-28 13:25:04 PST by jmasinter

  • Comment: Full Disk Encryption - loop on /dev/sda

    > May I follow the README example: "Example 7 - Boot > from USB-stick + encrypted root partition" except > losetup the raw device, /dev/sda? Yes. However, when kernel detects /dev/sda device, kernel may look for partition table, and when none is found, kernel may complain with cosmetic/no-harm error message. The initrd that build-initrd.sh creates attempts to...

    2012-01-28 00:47:02 PST by jariruusu

Our Numbers