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: Tue, 28 Feb 2017 16:37:57 -0800 From: Eric Dumazet <eric.dumazet@...il.com> To: Tom Herbert <tom@...bertland.com> Cc: Andy Lutomirski <luto@...capital.net>, Willem de Bruijn <willemdebruijn.kernel@...il.com>, Michael Kerrisk <mtk.manpages@...il.com>, netdev <netdev@...r.kernel.org>, Willem de Bruijn <willemb@...gle.com>, Linux API <linux-api@...r.kernel.org> Subject: Re: [PATCH RFC v2 00/12] socket sendmsg MSG_ZEROCOPY On Tue, 2017-02-28 at 16:28 -0800, Tom Herbert wrote: > The Mellanox team working on TLS offload pointed out to us that if > data is changed for a retransmit then it becomes trivial for someone > snooping to break the encryption. Sounds pretty scary and it would be > a shame if we couldn't use zero-copy in that use case :-( Hopefully we > can find a solution... Right, this is why offloading encryption over TCP is also hard ;)
Powered by blists - more mailing lists