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]
Date:   Fri, 11 May 2018 12:05:48 +0300
From:   Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To:     Ashwanth Goli <ashwanth@...eaurora.org>, netdev@...r.kernel.org,
        davem@...emloft.net
Cc:     pabeni@...hat.com, dsahern@...il.com, eric.dumazet@...il.com
Subject: Re: [PATCH] [PATCH net v2] ipv6: remove min MTU check for ipsec
 tunnels

On 5/11/2018 12:02 PM, Sergei Shtylyov wrote:

>> With 749439bfac "fix udpv6 sendmsg crash caused by too small MTU"
> 
>     When you cite a comnmit, you must specify at least 12-digit SHA1 and 
> enclose the summary in (""), not just "".
> 
>> ipsec tunnels that report a MTU less than IPV6_MIN_MTU are broken
>> even for packets that are smaller than IPV6_MIN_MTU.
>>
>> According to rfc2473#section-7.1
>>
>>      if the original IPv6 packet is equal or  smaller  than  the
>>      IPv6 minimum link MTU, the tunnel entry-point node
>>      encapsulates the original packet, and subsequently
>>      fragments the resulting IPv6 tunnel packet into IPv6
>>      fragments that do not exceed the Path MTU to the tunnel
>>      exit-point.
>>
>> Dropping the MTU check for ipsec tunnel destinations.
>>
>> Signed-off-by: Ashwanth Goli <ashwanth@...eaurora.org>
> [...]

    And you need to specify the patch version change log after the --- tear line.

MBR, Sergei

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ