Re: Announce loop-AES-v3.2a file/swap crypto package

[Jari Ruusu <jariruusu@users.sourceforge.net>]

markus reichelt wrote:
> * Jari Ruusu <jariruusu@users.sourceforge.net> wrote:
> > loop-AES changes since previous release:
> > - loop_twofish.c loop_serpent.c loop_blowfish.c modules included.
> >   They are not built by default. Add EXTRA_CIPHERS=y make parameter
> >   to build them.
> 
> Just curious, will the ciphers package also be continued/available
> separately as before or is it merged from now on into the loop-aes
> package?

Since loop-AES package now provides equivalent funtionality, it doesn't make
sense to maintain second package providing redundant functionality. The
merge was done because of difficulties getting versioned symbols to match
between two separately compiled packages. Even if separate package were to
be maintained (it won't be), it would not work well with versioned symbols.
If you want to blame someone for that, then blame mainline linux kbuild
guys.

I forgot to clearly say following in loop-AES-v3.2a README:

This command builds loop module with AES cipher integrated, as usual:

    make KEYSCRUB=y LINUX_SOURCE=/some/path/here

This command builds loop module with AES cipher integrated, and separate
twofish, serpent, and blowfish loop cipher modules:

    make KEYSCRUB=y EXTRA_CIPHERS=y LINUX_SOURCE=/some/path/here

This command builds only twofish, serpent, and blowfish loop cipher modules.
This assumes that kernel patch version of loop-AES is being used and is
enabled in kernel configuration:

    make EXTRA_CIPHERS=y BUILD_LOOP=n LINUX_SOURCE=/some/path/here

Key scrubbing, as enabled by KEYSCRUB=y make command line parameter,
currently only works for AES cipher. It has no effect on twofish, serpent,
and blowfish ciphers.

-- 
Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/