From: Dave Watson
Date: Tue, 29 Jan 2019 17:21:41 +
> Can we get a net->net-next merge when convenient?
This has now been done.
From: Dave Watson
Date: Tue, 29 Jan 2019 17:21:41 +
> I'd like to merge TLS1.3 support to net-next, which depends on this
> commit. Can we get a net->net-next merge when convenient? Thanks
Sure thing Dave, I'll let you know when that happens.
On 01/28/19 11:06 PM, David Miller wrote:
> From: Dave Watson
> Date: Sun, 27 Jan 2019 00:57:38 +
>
> > aead_request_set_crypt takes an iv pointer, and we change the iv
> > soon after setting it. Some async crypto algorithms don't save the iv,
> > so we need to save it in the tls_rec for asy
From: Dave Watson
Date: Sun, 27 Jan 2019 00:57:38 +
> aead_request_set_crypt takes an iv pointer, and we change the iv
> soon after setting it. Some async crypto algorithms don't save the iv,
> so we need to save it in the tls_rec for async requests.
>
> Found by hardcoding x64 aesni to use
aead_request_set_crypt takes an iv pointer, and we change the iv
soon after setting it. Some async crypto algorithms don't save the iv,
so we need to save it in the tls_rec for async requests.
Found by hardcoding x64 aesni to use async crypto manager (to test the async
codepath), however I don't
