Max Vozeler wrote: > I suppose one factor for choosing EXTRA_CIPHERS=n as default > is to keep the same defaults as for previous and current versions? Yes. > I'm only wondering because (if I had to guess), I would think that > people who like the ciphers built and installed probably outnumber > those who don't want/need them by default. Number of private emails that I have received about loop-AES/ciphers packages suggests most people only want AES, and as such, don't need those extra ciphers. > In any case: This sounds great. Should there be any work I can > contribute, please let me know. You can contribute by testing this new Makefile that I uploaded here: http://loop-aes.sourceforge.net/updates/Makefile-20070305.bz2 http://loop-aes.sourceforge.net/updates/Makefile-20070305.bz2.sign In addition to above mentioned Makefile, you need to copy *.c files from ciphers-v3.0e package to loop-AES-v3.1f source directory. And then run: make KEYSCRUB=y EXTRA_CIPHERS=y make tests EXTRA_CIPHERS=y Or whatever... In case someone is building new modules using above mentioned Makefile, and there are pre-existing modules from earlier module builds for same kernel, then one should remove old modules manually before compiling new modules. That is because new modules are installed to different directory on 2.6 kernels. 2.4 and older kernels still install modules in same directory as before. Old module directory, for 2.0, 2.2 and 2.4 kernels: /lib/modules/`uname -r`/block/ ^^^^^ New module directory, only for 2.6 kernels: /lib/modules/`uname -r`/extra/ ^^^^^ -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
