netdev - Re: [PATCH net-next] net/tls: Do not use async crypto for non-data records

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: <20190212.093528.434716184709943154.davem@davemloft.net>
Date:   Tue, 12 Feb 2019 09:35:28 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     vakul.garg@....com
Cc:     netdev@...r.kernel.org, borisp@...lanox.com, aviadye@...lanox.com,
        davejwatson@...com, doronrk@...com
Subject: Re: [PATCH net-next] net/tls: Do not use async crypto for non-data
 records

From: Vakul Garg <vakul.garg@....com>
Date: Mon, 11 Feb 2019 11:31:05 +0000

> Addition of tls1.3 support broke tls1.2 handshake when async crypto
> accelerator is used. This is because the record type for non-data
> records is not propagated to user application. Also when async
> decryption happens, the decryption does not stop when two different
> types of records get dequeued and submitted for decryption. To address
> it, we decrypt tls1.2 non-data records in synchronous way. We check
> whether the record we just processed has same type as the previous one
> before checking for async condition and jumping to dequeue next record.
> 
> Fixes: 130b392c6cd6b ("net: tls: Add tls 1.3 support")
> Signed-off-by: Vakul Garg <vakul.garg@....com>

Applied, thanks.