2017-09-24 11:05 GMT-04:00 Johannes Berg :
> On Sun, 2017-09-24 at 01:40 -0400, Xiang Gao wrote:
>> Currently, the aes_ccm.c and aes_gcm.c are almost line by line
>> copy of each other. This patch reduce code redundancy by moving
>> the code in these two files to
On Sun, 2017-09-24 at 13:21 -0400, Xiang Gao wrote:
>
> Do you mean to put more characters each line in the description
>
Huh, sorry, no - my bad. I was thinking of the code, not the
description at all.
For example here:
> -int ieee80211_aes_gcm_encrypt(struct crypto_aead *tfm, u8 *j_0, u8
2017-09-24 13:42 GMT-04:00 Johannes Berg :
> On Sun, 2017-09-24 at 13:21 -0400, Xiang Gao wrote:
>>
>> Do you mean to put more characters each line in the description
>>
> Huh, sorry, no - my bad. I was thinking of the code, not the
> description at all.
Oh yes, these
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Stephan Mueller
Fixed differently upstream as commit 2d97591ef43d ("crypto: af_alg -
consolidation of duplicate code")
The SGL is MAX_SGL_ENTS + 1 in size. The last SG
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Stephan Mueller
Fixed differently upstream as commit 2d97591ef43d ("crypto: af_alg -
consolidation of duplicate code")
The SGL is MAX_SGL_ENTS + 1 in size. The last SG
Hi Tudor,
> That Bluetooth SMP knows about the private key is pointless, since the
> detection of debug key usage is actually via the public key portion.
> With this patch set, the Bluetooth SMP will stop keeping a copy of the
> ecdh private key, except when using debug keys. This way we let the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Stephan Mueller
Fixed differently upstream as commit 2d97591ef43d ("crypto: af_alg -
consolidation of duplicate code")
The SGL is MAX_SGL_ENTS + 1 in size. The last SG
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stephan Mueller
Fixed differently upstream as commit 2d97591ef43d ("crypto: af_alg -
consolidation of duplicate code")
The SGL is MAX_SGL_ENTS + 1 in size. The last SG
Am Sonntag, 24. September 2017, 08:22:54 CEST schrieb Stephan Müller:
Hi Herbert,
(private)
> Hi Herbert,
>
> The two patches together fix a kernel crash that can be triggered via
> AF_ALG when using authenc() with zero plaintext.
>
> The changes are also tested to verify that the hashing on
On Thu, Sep 21, 2017 at 9:43 AM, Janani Sankara Babu
wrote:
> This patch solves the warning shown by the checkpatch script
> WARNING: externs should be avoided in .c files
I'm afraid here too the feedback is the same - you are working on the
Linus master tree, therefore you
In case the caller provides an SG with zero data, prevent a kmap of the
page pointed to by the SG. In this case, it is possible that the page
does not exist.
This fixes a crash in authenc() when the plaintext is zero and thus the
encryption operation is a noop. In this case, no input data exists
Hi Herbert,
The two patches together fix a kernel crash that can be triggered via
AF_ALG when using authenc() with zero plaintext.
The changes are also tested to verify that the hashing on null data
is still supported.
I suspect that the vulnerability fixed with patch 1 is present in
abklcipher
On Sun, 2017-09-24 at 01:40 -0400, Xiang Gao wrote:
> Currently, the aes_ccm.c and aes_gcm.c are almost line by line
> copy of each other. This patch reduce code redundancy by moving
> the code in these two files to crypto/aead_api.c to make it a
> higher level aead api. The aes_ccm.c and
Hi Janani,
On Thu, Sep 21, 2017 at 9:39 AM, Janani Sankara Babu
wrote:
> This patch is created to solve the following warning shown by the checkpatch
> script Warning: Replace all occurences of (1<
> Signed-off-by: Janani Sankara Babu
On Mon, 2017-09-25 at 12:56 +0800, Herbert Xu wrote:
> On Sun, Sep 24, 2017 at 07:42:46PM +0200, Johannes Berg wrote:
> >
> > Unrelated to this, I'm not sure whose tree this should go through -
> > probably Herbert's (or DaveM's with his ACK? not sure if there's a
> > crypto tree?) or so?
>
>
On Sun, Sep 24, 2017 at 07:42:46PM +0200, Johannes Berg wrote:
>
> Unrelated to this, I'm not sure whose tree this should go through -
> probably Herbert's (or DaveM's with his ACK? not sure if there's a
> crypto tree?) or so?
Since you're just rearranging code invoking the crypto API, rather
16 matches
Mail list logo