Am 23.07.2018 um 09:59 schrieb Ralf Mardorf:
On Mon, 23 Jul 2018 08:47:51 +0200, Peter Nabbefeld wrote:
CONFIG_CRYPTO_SALSA20_X86_64=m
I don't know if this helps. 4.17.9-1 moved from Staging to Testing and
at least the version from Staging contains CONFIG_CRYPTO_SALSA20.
$ uname -rm; zgrep SALSA /proc/config.gz
4.17.9-1-ARCH x86_64
CONFIG_CRYPTO_SALSA20=m
$ grep SALSA /lib/modules/4.17.9-1-ARCH/build/.config
CONFIG_CRYPTO_SALSA20=m
However, actually it now also contains CONFIG_CRYPTO_SALSA20_X86_64.
$ asp update
[snip]
$ asp checkout linux-headers
[snip]
$ grep pkg.e.= linux/trunk/PKGBUILD
pkgver=4.17.9
pkgrel=1
$ grep SALSA linux/trunk/config
CONFIG_CRYPTO_SALSA20=m
CONFIG_CRYPTO_SALSA20_X86_64=m
Thank You, Ralph! Tried to get that file from testing but couldn't find
out how. Just activating the repo didn't help, probably I'd have to use
some other mirror.
It seems, CONFIG_CRYPTO_SALSA20 activates the external API (to be used
by modules and/or applications) while CONFIG_CRYPTO_SALSA20_X86_64
provides the implementation, so it *should* help (if this is the stream
cipher used by bluez).
So waiting for the next update. :)
Kind regards
Peter
