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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <79ebb0ba-2b7d-edd0-0cd7-0940441f9db4@gmail.com>
Date:   Wed, 28 Aug 2019 16:47:11 -0700
From:   Gregory Rose <gvrose8192@...il.com>
To:     David Miller <davem@...emloft.net>
Cc:     netdev@...r.kernel.org, pshelar@....org, joe@...d.net.nz
Subject: Re: [PATCH V3 net 1/2] openvswitch: Properly set L4 keys on "later"
 IP fragments

On 8/28/2019 2:54 PM, David Miller wrote:
> From: Greg Rose <gvrose8192@...il.com>
> Date: Tue, 27 Aug 2019 07:58:09 -0700
>
>> When IP fragments are reassembled before being sent to conntrack, the
>> key from the last fragment is used.  Unless there are reordering
>> issues, the last fragment received will not contain the L4 ports, so the
>> key for the reassembled datagram won't contain them.  This patch updates
>> the key once we have a reassembled datagram.
>>
>> The handle_fragments() function works on L3 headers so we pull the L3/L4
>> flow key update code from key_extract into a new function
>> 'key_extract_l3l4'.  Then we add a another new function
>> ovs_flow_key_update_l3l4() and export it so that it is accessible by
>> handle_fragments() for conntrack packet reassembly.
>>
>> Co-authored by: Justin Pettit <jpettit@....org>
>> Signed-off-by: Greg Rose <gvrose8192@...il.com>
> Applied with Co-authored-by fixed.
Thanks for fixing that up Dave.

- Greg

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ