linux-kernel - Re: [PATCH v3 1/3] crypto: engine - permit to enqueue aead

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9d89727b-f3cb-3322-6513-962e9df63ca8@st.com>
Date:   Fri, 6 Oct 2017 09:26:07 +0000
From:   Fabien DESSENNE <fabien.dessenne@...com>
To:     Herbert Xu <herbert@...dor.apana.org.au>
CC:     "David S . Miller" <davem@...emloft.net>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Alexandre TORGUE <alexandre.torgue@...com>,
        "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Benjamin GAIGNARD <benjamin.gaignard@...com>,
        Lionel DEBIEVE <lionel.debieve@...com>,
        Ludovic BARRE <ludovic.barre@...com>,
        Corentin Labbe <clabbe.montjoie@...il.com>
Subject: Re: [PATCH v3 1/3] crypto: engine - permit to enqueue aead_request

OK, I will send an initial version without the AEAD part.


On 05/10/17 05:39, Herbert Xu wrote:
> On Tue, Oct 03, 2017 at 07:48:08AM +0000, Fabien DESSENNE wrote:
>> It looks like there is no more activity around this "crypto_engine
>> interface clean up" task.
>> This unfortunately has been blocking the introduction of this new STM32
>> crypto driver for 3 months now.
>> Would it make sense to have this driver reviewed first, and then
>> reworked (I expect minor update here) when the interface update is ready?
> Hmm, is it possible to disable the AEAD part of the driver first?
>
> Cheers,