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  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]
Date:   Thu, 28 May 2020 09:08:00 +0300
From:   Boris Pismenny <borisp@...lanox.com>
To:     Jakub Kicinski <kuba@...nel.org>,
        Tariq Toukan <tariqt@...lanox.com>
Cc:     "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
        Maxim Mikityanskiy <maximmi@...lanox.com>,
        Saeed Mahameed <saeedm@...lanox.com>
Subject: Re: [PATCH net-next] net/tls: Add force_resync for driver resync

On 28/05/2020 1:32, Jakub Kicinski wrote:
> On Wed, 27 May 2020 12:25:26 +0300 Tariq Toukan wrote:
>> This patch adds a field to the tls rx offload context which enables
>> drivers to force a send_resync call.
>>
>> This field can be used by drivers to request a resync at the next
>> possible tls record. It is beneficial for hardware that provides the
>> resync sequence number asynchronously. In such cases, the packet that
>> triggered the resync does not contain the information required for a
>> resync. Instead, the driver requests resync for all the following
>> TLS record until the asynchronous notification with the resync request
>> TCP sequence arrives.
>>
>> A following series for mlx5e ConnectX-6DX TLS RX offload support will
>> use this mechanism.
> Please document this, in tls-offload.rst.
Sure, I'll take a look at it next week

Powered by blists - more mailing lists