The reason I'd create a loop_aes.c, is that suse 10.1 already has a loop.c, so it's impractical to just replace that one with the one in the loop-AES package. It also seems they've changed the architecture a bit, and instead of building thing into xfer_functs[MAX_LO_CRYPT] inside of loop.c, modules such as loop_blowfish.c (not in the official linux sources), make a callback to get this registration. I don't want to provide compiled objects, only source files, loop_aes.[ch], etc. And, since the ioctl LOOP_MULTI_KEY_SETUP_V3 is not supported by the standard losetup, it'd have to change as well, but any code added there would be inside a conditional. - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
