Re: [PATCH RFC v2 00/12] socket sendmsg MSG_ZEROCOPY
From: Eric Dumazet <hidden>
Date: 2017-03-01 00:37:57
Also in:
linux-api
Possibly related (same subject, not in this thread)
- 2017-03-02 · Re: [PATCH RFC v2 00/12] socket sendmsg MSG_ZEROCOPY · Andy Lutomirski <luto@amacapital.net>
- 2017-03-01 · Re: [PATCH RFC v2 00/12] socket sendmsg MSG_ZEROCOPY · Eric Dumazet <hidden>
- 2017-03-01 · Re: [PATCH RFC v2 00/12] socket sendmsg MSG_ZEROCOPY · David Miller <davem@davemloft.net>
- 2017-03-01 · Re: [PATCH RFC v2 00/12] socket sendmsg MSG_ZEROCOPY · David Miller <davem@davemloft.net>
- 2017-03-01 · Re: [PATCH RFC v2 00/12] socket sendmsg MSG_ZEROCOPY · Tom Herbert <hidden>
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 ;)