netdev - Re: [PATCH net-next] ipip: Add room for user-specified custom header

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: <20130814.133929.975837205960955245.davem@davemloft.net>
Date:	Wed, 14 Aug 2013 13:39:29 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	kristian.evensen@...il.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] ipip: Add room for user-specified custom
 header

From: Kristian Evensen <kristian.evensen@...il.com>
Date: Mon, 12 Aug 2013 10:39:38 +0200

> This patch adds support for specifying the size of a custom header to be
> inserted between the two IP headers. The actual content will be inserted later,
> for example by a module that is attached to a hook.
> 
> A use-case for the feature provided by this patch is to ease the implementation
> of custom tunneling protocols. Instead of implementing them directly in the
> kernel and having to look out for changes in the kernel behavior/APIs, a
> tunneling protocol can be implemented as an independent module.
> 
> To avoid breaking user space (by updating ip_tunnel_params), it is only possible
> to specify the custom header length when an IPIP-tunnel is created using
> netlink-messages.
> 
> Signed-off-by: Kristian Evensen <kristian.evensen@...il.com>

Sorry I'm not even going to consider applying this until you post
use-cases for this feature, because right now it just looks like a
random way to facilitate some third party proprietary kernel module
or similar.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html