On Fri, March 31, 2006 20:10, markus reichelt wrote: > Additionally to Jari's comment, I bet that if you post this question > to dm-crypt's mailinglist, you'll read quite the opposite :-) Jim, please do to dm-crypt's mailinglist and maybe we can engage a *useful* discussion as to why would anybody use loop-aes/dm-crypt. I'm in a similiar position as Jim as I've chosen loop-aes (Thanks, Jari!) when there was only cryptoloop in mainline. I like loop-aes, but it's the only 3rd party module I have to build and using a mainline solution would be.....neat. > Just being curious, why not stick to loop-aes? As it seems it has > served you well over the years, being both stable and secure. I believe that it'd be a good thing to make crypto simpler (not less secure!) and having to build loop.ko seperatly is easy for the readers of this group and it may be easy for the kernel-maintainer of $DISTRO, but it's not simpler than just using $SECURE_MAINLINE_CRYPTO, whatever that'd be. Thanks, Christian. -- BOFH excuse #442: Trojan horse ran out of hay - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
