diff options
author | Ard Biesheuvel <ardb@kernel.org> | 2019-11-08 13:22:08 +0100 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2019-11-17 09:02:39 +0800 |
commit | 5fb8ef25803ef33e2eb60b626435828b937bed75 (patch) | |
tree | 156401ad072c1acc18f74cbdf8eb31859191b9ac /lib/crypto/Makefile | |
parent | 746b2e024c67aa605ac12d135cd7085a49cf9dc4 (diff) | |
download | linux-5fb8ef25803ef33e2eb60b626435828b937bed75.tar.gz linux-5fb8ef25803ef33e2eb60b626435828b937bed75.tar.bz2 linux-5fb8ef25803ef33e2eb60b626435828b937bed75.zip |
crypto: chacha - move existing library code into lib/crypto
Currently, our generic ChaCha implementation consists of a permute
function in lib/chacha.c that operates on the 64-byte ChaCha state
directly [and which is always included into the core kernel since it
is used by the /dev/random driver], and the crypto API plumbing to
expose it as a skcipher.
In order to support in-kernel users that need the ChaCha streamcipher
but have no need [or tolerance] for going through the abstractions of
the crypto API, let's expose the streamcipher bits via a library API
as well, in a way that permits the implementation to be superseded by
an architecture specific one if provided.
So move the streamcipher code into a separate module in lib/crypto,
and expose the init() and crypt() routines to users of the library.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'lib/crypto/Makefile')
-rw-r--r-- | lib/crypto/Makefile | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/lib/crypto/Makefile b/lib/crypto/Makefile index 63de4cb3fcf8..0ce40604e104 100644 --- a/lib/crypto/Makefile +++ b/lib/crypto/Makefile @@ -1,5 +1,9 @@ # SPDX-License-Identifier: GPL-2.0 +# chacha is used by the /dev/random driver which is always builtin +obj-y += chacha.o +obj-$(CONFIG_CRYPTO_LIB_CHACHA_GENERIC) += libchacha.o + obj-$(CONFIG_CRYPTO_LIB_AES) += libaes.o libaes-y := aes.o |