crypto loopback & recompiling kernels

[davidHarris]

Im trying to recompile the Knoppix kernel for reasons related to crypto loopback.
the /usr/src/linux* directory say the kernel is a vanilla 2.4.20 kernel with only xfs & commandline mods but the .config file has none of the options needed for crypto, e.g.; CONFIG_CRYPTO=m etc.

since you have to patch the vanilla kernel with the patch-int stuff etc is there a a copy of the patched kernel source used for Knoppix available? and the real config file?[/i]

[BillyBobber]

I tried this too. I couldn't get the patches to work so I simply downloaded the kernel source and rebuilt the kernel with the correct options set. It took about 20 builds to get everything to finally work. Keep in mind that only a certain version of the kernel would fly with the crypto modules. I have a 1.5 TB crypto volume. It's cool. The problem is that since the crypto work is all done in software, that volume is very, very, very slow. If you delete large files, the system slows down to a crawl to the point where the mouse cursor can take 10 seconds to react to a mouse movement.

[davidHarris]

I tried this too. I couldn't get the patches to work so I simply downloaded the kernel source and rebuilt the kernel with the correct options set. It took about 20 builds to get everything to finally work. Keep in mind that only a certain version of the kernel would fly with the crypto modules.

there doesnt appear to be any info anywhere as to which crypto modules work with which kernels. If that were true it might explain why explain why I cant get crypto working (& which is why I wanted to rebuild the knoppix version of the kernel). I dont think aes is built into the kernel.

AFAIK the knoppix kernel source (with patches applied by the knoppix team) isnt available on this site & that would be helpful as a sanity check.

[eadz]

I did this. I just downloaded the kernel source, applied the patch, copied the .config to the source dir, ran "make oldconfig", and then built the kernel and modules.

Then you have to add the modules to /lib/modules and the kernel to the miniroot.gz.

[Dave_Bechtel]

--Two solutions (actually three)

1. Faster processor (maybe dual Athlons)
2. More RAM
3. shrink the volume

3comedy: delete all that pr0n and it will speed up just fine!

I tried this too. I couldn't get the patches to work so I simply downloaded the kernel source and rebuilt the kernel with the correct options set. It took about 20 builds to get everything to finally work. Keep in mind that only a certain version of the kernel would fly with the crypto modules. I have a 1.5 TB crypto volume. It's cool. The problem is that since the crypto work is all done in software, that volume is very, very, very slow. If you delete large files, the system slows down to a crawl to the point where the mouse cursor can take 10 seconds to react to a mouse movement.

[davidHarris]

-

3comedy: delete all that pr0n and it will speed up just fine!

Im sceptical; 1.5Tb porn? thats way more than me, I'd like to see that.
no really I'd like to see that

[davidHarris]

I did this. I just downloaded the kernel source, applied the patch, copied the .config to the source dir, ran "make oldconfig", and then built the kernel and modules.

Then you have to add the modules to /lib/modules and the kernel to the miniroot.gz.

But that was my point: the .config file contains no crypto related options in it, so after you patch the kernel with the international patch how is the .config helping you to select, for example, cryptoapi, cryptoloop, cipher-aes etc.
After I do all the patching cipher module building etc etc All I get after doing losetup ... is ioctl: LOOP_SET_STATUS: Invalid argument
Can you tell me the kernel you used and what patches you used to get functioning loopback crypto.

[eadz]

I did this. I just downloaded the kernel source, applied the patch, copied the .config to the source dir, ran "make oldconfig", and then built the kernel and modules.

Then you have to add the modules to /lib/modules and the kernel to the miniroot.gz.

But that was my point: the .config file contains no crypto related options in it, so after you patch the kernel with the international patch how is the .config helping you to select, for example, cryptoapi, cryptoloop, cipher-aes etc.
After I do all the patching cipher module building etc etc All I get after doing losetup ... is ioctl: LOOP_SET_STATUS: Invalid argument
Can you tell me the kernel you used and what patches you used to get functioning loopback crypto.

Yes, that's why you :

make oldconfig

which uses the .config you supply ( i.e. you've put the .config from knoppix into your kernel directory where you are compiling ) and it just asks for the new options.

Hmm, although that error, LOOP_SET_STATUS, looks like a modprobe / mount error. You may not be using the correct mount options. I.e. are you doing losetup with all the crypto options?

[garyng]

As far as I know, the loopback device for crypto is a dropped in replacement (loop.o) which is built seperately from the kernel. There is no options in the kernel build tree for that.

[eadz]

As far as I know, the loopback device for crypto is a dropped in replacement (loop.o) which is built seperately from the kernel. There is no options in the kernel build tree for that.

You can build it into the kernel. And yep, I think it is called loop.o when it's compiled as a module. The Knoppix compressed loop is cloop.o .