Adding "EXTRA_CIPHERS=y" at make time enables building of loop devices that support Blowfish, Twofish, Serpent, etc. in addition to the one that uses AES. As far as I'm concerned, those kernel modules could be built unconditionally by the ebuild. It'd be just as nice, of course, to let the user enable that feature with a use flag, say extraloopciphers or whatever. Reproducible: Always
Hello, That's true that this can be nice... But I don't wish to maintain the issue resulting from these other ciphers. The AES option is the one most user should use. It has good performance and strength. So I will not add this for now. Thanks