vinnakota chaitanya wrote: > Molle Bestefich wrote: > > Use loop-aes, it's absolutely fabulous. > > > > It works great with 2.4 as well as 2.6. > > > > Instructions here. > > http://loop-aes.sourceforge.net/loop-AES.README > > Thanks for the suggestion. > Now I've the following two issues: > > 1. The target device is fat filesystem formatted. The > target kernel image do not contain the fat filesystem > module. The target device [ i.e. /dev/md0 ] is > mounted by the host through USB interface. Hence, in > this case the host's fat filesystem code is used. > Will loop-aes work in this situation. Loop-aes functions as a loop device. It reads and writes encrypted data to/from either a file or a block device such as /dev/md0 in your case. In the other end it gives you a block device, we'll call it /dev/loop0, from which you can read/write your unencrypted data. Loop-aes does not care which filesystems you stick on /dev/loop0, and it does not care whether your kernel happens to be able to understand and mount those filesystems. I'm curious. How does your "target device" export the /dev/loop0 to the "host device" through USB? > 2. We were asked to use blow_fish algorithm instead. > So, how to go about it, are there any modules like > loop-aes or should I consider the hooks > raid5_make_request and raid5_end_read_request > for encryption and decryption I would without a doubt spare myself the trouble and just use loop-aes. As I've said, it's great. But feel free to implement your own solution. I can't give any recommendations on how. You might want to check out twofish, in which Mr. Schneier et al has fixed "a security problem" of some sort. Not sure which. Presumably Wikipedia or Google knows. - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
