netdev - Re: [PATCH] net: Fragment large datagrams even when IP

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMrnHh4_yU586bGV9hG0pcbnwPkdNDqrimmipkXam=fOzh3nEg@mail.gmail.com>
Date:	Sat, 9 Jul 2016 02:21:58 +0300
From:	Alexey Kuznetsov <kuznet@....inr.ac.ru>
To:	netdev@...r.kernel.org
Subject: Re: [PATCH] net: Fragment large datagrams even when IP_HDRINCL is set.

Hello!

I can tell why it has not been done initially.

Main problem was in IP options, which can be present in raw packet.
They have to be properly fragmented, some options are to be deleted
on fragments. Not that it is too complicated, it is just boring and ugly
and inconsistent with IP_HDRINCL logic.

So, it was done in logically consistent way: did you order IP_HDRINCL?
Please, then deal with fragments yourself.

Alexey