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
| ||
|
Date: Mon, 13 Jul 2020 18:02:10 -0700 (PDT) From: David Miller <davem@...emloft.net> To: borisp@...lanox.com Cc: kuba@...nel.org, john.fastabend@...il.com, daniel@...earbox.net, tariqt@...lanox.com, netdev@...r.kernel.org Subject: Re: [PATCH] tls: add zerocopy device sendpage From: Boris Pismenny <borisp@...lanox.com> Date: Tue, 14 Jul 2020 01:15:26 +0300 > On 13/07/2020 22:05, David Miller wrote: >> From: Boris Pismenny <borisp@...lanox.com> >> Date: Mon, 13 Jul 2020 10:49:49 +0300 >> >> Why can't the device generate the correct TLS signature when >> offloading? Just like for the protocol checksum, the device should >> load the payload into the device over DMA and make it's calculations >> on that copy. > > Right. The problematic case is when some part of the record is already > received by the other party, and then some (modified) data including > the TLS authentication tag is re-transmitted. Then we must copy to avoid this.
Powered by blists - more mailing lists