From owner-freebsd-security@FreeBSD.ORG  Sun Sep  4 21:47:46 2011
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2C84E1065674
	for <freebsd-security@freebsd.org>;
	Sun,  4 Sep 2011 21:47:46 +0000 (UTC)
	(envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
	by mx1.freebsd.org (Postfix) with ESMTP id E53028FC19
	for <freebsd-security@freebsd.org>;
	Sun,  4 Sep 2011 21:47:45 +0000 (UTC)
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3])
	by phk.freebsd.dk (Postfix) with ESMTP id 8C5BB5E31
	for <freebsd-security@freebsd.org>;
	Sun,  4 Sep 2011 21:27:51 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.14.5/8.14.5) with ESMTP id p84LRpFQ003948
	for <freebsd-security@freebsd.org>; Sun, 4 Sep 2011 21:27:51 GMT
	(envelope-from phk@phk.freebsd.dk)
To: freebsd-security@freebsd.org
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Content-Type: text/plain; charset=ISO-8859-1
Date: Sun, 04 Sep 2011 21:27:51 +0000
Message-ID: <3947.1315171671@critter.freebsd.dk>
Subject: VIMAGE and OpenVPN idea...
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Sep 2011 21:47:46 -0000


Here is an idea for an interesting little project:

Imagine a firewall where all the external interfaces are
confined in a jail which has no IP-connectivity to the
rest of the machine.

Start OpenVPN outside the jail, have it setup a two-way pipe
and fork a childprocess, which attaches to the jail and performs
out all public-side socket operations inside the jail, passing
only the raw encrypted packets over the pipe.

Tada:  Nothing in the jail can be hacked...

Only problem is:  OpenVPN doesn't know this trick.

But how hard could that be ?

Somebody[tm] should do that...


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.