netdev - Re: [PATCH net-next 0/2] tls: Add TLS 1.3 hardware offload support

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: <CAKaoeS3rRk8FGv+zb_vYuYoMAPe7gAsgxq_TKG4OcT5QkKOwjA@mail.gmail.com>
Date: Wed, 31 Dec 2025 11:34:04 -0800
From: Rishikesh Jethwani <rjethwani@...estorage.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, saeedm@...dia.com, tariqt@...dia.com, 
	mbloch@...dia.com, borisp@...dia.com, john.fastabend@...il.com, 
	kuba@...nel.org, sd@...asysnail.net, davem@...emloft.net
Subject: Re: [PATCH net-next 0/2] tls: Add TLS 1.3 hardware offload support

On Wed, Dec 31, 2025 at 1:17 AM Andrew Lunn <andrew@...n.ch> wrote:
>
> > Tested on the following hardware:
> > - Broadcom BCM957608 (Thor 2)
> > - Mellanox ConnectX-6 Dx (Crypto Enabled)
> >
> > Both TX and RX hardware offload verified working with:
> > - TLS 1.3 AES-GCM-128
> > - TLS 1.3 AES-GCM-256
>
> You don't patch any broadcom driver. Does that mean it just works? The
> changes to the core are all that are needed for BCM957608?

The upstream Broadcom bnxt_en driver does not yet support kTLS offload.
Testing was performed using the out-of-tree driver version
bnxt_en-1.10.3-235.1.154.0,
which works without modifications.