Date: Sun, 01 Feb 2015 21:07:16 -0800 (PST)
Message-Id: <20150201.210716.588479604128207372.davem@davemloft.net>
To: dwmw2@infradead.org
Cc: mst@redhat.com, herbert@gondor.apana.org.au, eric.dumazet@gmail.com,
        jan.kiszka@siemens.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] tun: orphan an skb on tx
From: David Miller <davem@davemloft.net>
In-Reply-To: <1422826183.11044.72.camel@infradead.org>
References: <1422797630.11044.32.camel@infradead.org>
	<20150201.121948.998046471405758397.davem@davemloft.net>
	<1422826183.11044.72.camel@infradead.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 928
Lines: 22

From: David Woodhouse <dwmw2@infradead.org>
Date: Sun, 01 Feb 2015 21:29:43 +0000

> I really was looking for some way to push down something like an XFRM
> state into the tun device and just say "shove them out here until I tell
> you otherwise".

People decided to use TUN and push VPN stuff back into userspace,
and there are repercussions for that decision.

I'm not saying this to be mean or whatever, but I was very
disappointed when userland IPSEC solutions using TUN started showing
up.

We might as well have not have implemented the IPSEC stack at all,
because as a result of the userland VPN stuff our IPSEC stack is
largely unused except by a very narrow group of users.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/