Re: [PATCH v2 2/5] crypto: stm32 - Support for STM32 CRC32 crypto module

On 21 March 2017 at 20:43, Fabien Dessenne wrote: > This module registers a CRC32 ("Ethernet") and a CRC32C (Castagnoli) > algorithm that make use of the STMicroelectronics STM32 crypto hardware. > > Theses algorithms are compatible with the little-endian generic ones. >

Re: [PATCH] arm64: dts: ls1012a: add crypto node

On Wed, Mar 22, 2017 at 02:29:39PM +0200, Horia Geantă wrote: > LS1012A has a SEC v5.4 security engine. > > Signed-off-by: Horia Geantă > --- > arch/arm64/boot/dts/freescale/fsl-ls1012a-frdm.dts | 9 +++ > arch/arm64/boot/dts/freescale/fsl-ls1012a-qds.dts | 9 +++ >

[ANNOUNCE] Linux Security Summit 2017 - CFP

== ANNOUNCEMENT AND CALL FOR PARTICIPATION LINUX SECURITY SUMMIT 2017 14-15 September

Re: [PATCH] crypto: xts,lrw - fix out-of-bounds write after kmalloc failure

From: Eric Biggers Date: Thu, 23 Mar 2017 13:39:46 -0700 > From: Eric Biggers > > In the generic XTS and LRW algorithms, for input data > 128 bytes, a > temporary buffer is allocated to hold the values to be XOR'ed with the > data before and after

[PATCH] crypto: xts,lrw - fix out-of-bounds write after kmalloc failure

From: Eric Biggers In the generic XTS and LRW algorithms, for input data > 128 bytes, a temporary buffer is allocated to hold the values to be XOR'ed with the data before and after encryption or decryption. If the allocation fails, the fixed-size buffer embedded in the

Re: crypto: out-of-bounds write in pre_crypt

Hi Dmitry, On Thu, Mar 23, 2017 at 11:51:30AM +0100, Dmitry Vyukov wrote: > Hello, > > I've got the following report while running syzkaller fuzzer. > init_crypt ignores kmalloc failure, which later leads to out-of-bounds > writes in ptr_crypt. On commit >

Re: [PATCH] md5: remove from lib and only live in crypto

On Thu, Mar 16, 2017 at 03:18:57PM +0100, Jason A. Donenfeld wrote: > The md5_transform function is no longer used any where in the tree, > except for the crypto api's actual implementation of md5, so we can drop > the function from lib and put it as a static function of the crypto > file, where

Re: next build: 208 builds: 9 failed, 199 passed, 857 errors, 444 warnings (next-20170323)

t > <linux-ker...@vger.kernel.org>, linux-crypto@vger.kernel.org, > linux-m...@linux-mips.org, "Steven J. Hill" <steven.h...@cavium.com>, Ralf > Baechle <r...@linux-mips.org> > Subject: Re: next build: 208 builds: 9 failed, 199 passed, 857 errors, 444 > warnin

[PATCH] crypto: ccp - Make some CCP DMA channels private

The CCP registers its queues as channels capable of handling general DMA operations. The NTB driver will use DMA if directed, but as public channels can be reserved for use in asynchronous operations some channels should be held back as private. Since the public/private determination is handled at

Re: [PATCH] crypto: ixp4xx - Use sg_virt()

From: Geliang Tang Date: Thu, 23 Mar 2017 21:16:30 +0800 > Use sg_virt() instead of open-coding it. > > Signed-off-by: Geliang Tang Acked-by: David S. Miller

Re: next build: 208 builds: 9 failed, 199 passed, 857 errors, 444 warnings (next-20170323)

On Thu, Mar 23, 2017 at 6:46 AM, kernelci.org bot wrote: > acs5k_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches > > Warnings: > :1328:2: warning: #warning syscall arch_prctl not implemented [-Wcpp] > :1328:2: warning: #warning syscall arch_prctl not

[PATCH] crypto: ixp4xx - Use sg_virt()

Use sg_virt() instead of open-coding it. Signed-off-by: Geliang Tang --- drivers/crypto/ixp4xx_crypto.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/crypto/ixp4xx_crypto.c b/drivers/crypto/ixp4xx_crypto.c index 7868765..771dd26 100644 ---

Re: Question - seeding the hw pseudo random number generator

Am Donnerstag, 23. März 2017, 10:44:06 CET schrieb Herbert Xu: Hi Herbert, > On Thu, Mar 23, 2017 at 09:23:07AM +0100, Corentin Labbe wrote: > > Problem with this conversion, a huge regression for user space. > > Using hwrng is simple as cat /dev/hwrng. > > Using algif_rng via AF_ALG is ...

Re: Question - seeding the hw pseudo random number generator

Am Donnerstag, 23. März 2017, 09:03:23 CET schrieb Harald Freudenberger: Hi Harald, > I'll have a look on it. Currently the s390/crypto/prng seeds itself with > an algorithm based on the jitter of the very fine granular hardware > clock of a s390 machine. There were some thoughts and

[PATCH] padata: avoid race in reordering

Under extremely heavy uses of padata, crashes occur, and with list debugging turned on, this happens instead: [87487.298728] WARNING: CPU: 1 PID: 882 at lib/list_debug.c:33 __list_add+0xae/0x130 [87487.301868] list_add corruption. prev->next should be next (b17abfc043d0), but was

Re: [PATCH] md5: remove from lib and only live in crypto

POKE?

Re: Question - seeding the hw pseudo random number generator

On Thu, Mar 23, 2017 at 09:23:07AM +0100, Corentin Labbe wrote: > > Problem with this conversion, a huge regression for user space. > Using hwrng is simple as cat /dev/hwrng. > Using algif_rng via AF_ALG is ... unusable for the moment. > Perhaps creating an user space tool (prng-tool which

Re: [PATCH v3 1/3] clk: meson-gxbb: expose clock CLKID_RNG0

On Wed, Mar 22, 2017 at 08:24:08AM -0700, Kevin Hilman wrote: > > Because this will be causing conflicts with both the platform (amlogic) > tree and the clk tree, could provide an immutable branch where these are > applied to help us handle these conflicts? If you apply the same patches to your

Re: race condition in kernel/padata.c

On Thu, Mar 23, 2017 at 12:03:43AM +0100, Jason A. Donenfeld wrote: > Hey Steffen, > > WireGuard makes really heavy use of padata, feeding it units of work > from different cores in different contexts all at the same time. For > the most part, everything has been fine, but one particular user has

Re: Question - seeding the hw pseudo random number generator

On Mon, Mar 20, 2017 at 09:28:58PM +0800, Herbert Xu wrote: > On Mon, Mar 20, 2017 at 12:19:32PM +0530, PrasannaKumar Muralidharan wrote: > > > > AF_ALG interface for rng does have seeding support. I think hw_random > > does not provide seeding support intentionally as I understand that > > True

Re: Question - seeding the hw pseudo random number generator

On 03/20/2017 02:39 PM, Stephan Müller wrote: > Am Montag, 20. März 2017, 14:28:58 CET schrieb Herbert Xu: > > Hi Herbert, > >> On Mon, Mar 20, 2017 at 12:19:32PM +0530, PrasannaKumar Muralidharan wrote: >>> AF_ALG interface for rng does have seeding support. I think hw_random >>> does not provide