Delivery-Date: Mon, 15 Feb 2016 10:56:10 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 58DC51E07FE;
	Mon, 15 Feb 2016 10:56:08 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A60B2391E2;
	Mon, 15 Feb 2016 15:56:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id BF3363919D
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 15:55:57 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id zP91IXh6B9n4 for <tor-talk@lists.torproject.org>;
 Mon, 15 Feb 2016 15:55:57 +0000 (UTC)
Received: from gil.mayfirst.org (gil.mayfirst.org [216.66.23.48])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id A6AD1390AC
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 15:55:57 +0000 (UTC)
Received: from gil.mayfirst.org (unknown [127.0.0.1])
 by gil.mayfirst.org (Postfix) with ESMTP id 347F35E98
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 10:55:53 -0500 (EST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender:
 nathanfreitas@gil.mayfirst.org) with ESMTPSA id 1F5955E79
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
 by mailauth.nyi.internal (Postfix) with ESMTP id 638E4209DF
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 10:55:54 -0500 (EST)
Received: from web5 ([10.202.2.215])
 by compute4.internal (MEProxy); Mon, 15 Feb 2016 10:55:54 -0500
Received: by web5.nyi.internal (Postfix, from userid 99)
 id 4364EA73065; Mon, 15 Feb 2016 10:55:54 -0500 (EST)
Message-Id: <1455551754.2099961.521734066.638EF9EE@webmail.messagingengine.com>
X-Sasl-Enc: f56IE19SoVTxHioUVEiRRZZFYV6eSkz1P1D+Hfxv/xr5 1455551754
From: Nathan Freitas <nathan@freitas.net>
To: tor-talk@lists.torproject.org
MIME-Version: 1.0
X-Mailer: MessagingEngine.com Webmail Interface - ajax-aeec9b65
Date: Mon, 15 Feb 2016 10:55:54 -0500
In-Reply-To: <512753.0fd66affa8c16a41619b165033156a1fd819c470@popretr.messagingengine.com>
References: <512753.f0610b5a2ba80e2b5e307afc6982286451c15c63@popretr.messagingengine.com>
 <56BDDEB4.1070107@openmailbox.org>
 <1455288823.340246.519465714.3E8E8420@webmail.messagingengine.com>
 <56BE4071.50609@openmailbox.org>
 <CAJVRA1RabMrMAcyO3Y4hYcJoWQQRmOQR=_vBv7fCQiCVo=k5GQ@mail.gmail.com>
 <512753.0fd66affa8c16a41619b165033156a1fd819c470@popretr.messagingengine.com>
 <56C06102.5010508@openmailbox.org>
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [tor-talk] orplug,
 an Android firewall with per-app Tor circuit isolation
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Sun, Feb 14, 2016, at 06:12 AM, Rusty Bird wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hi coderman,
> 
> > with VPN approach you don't get to control traffic outside routed 
> > range, or before VPN activates, or fail-safe if it drops 
> > un-expectedly, or ...
> 
> I heard that Android VPNs can have some sort of fail-closed mode, does
> this apply to Orbot?

No. That only works for the built-in VPNs (PPTP, IPSec), and not for the
App/API-based VPNs.

> > note that a tor enforcing gateway approach is preferable to 
> > transparent proxy, security wise. e.g. corridor. i haven't seen
> > this applied to Android env, which might be interesting safety
> > buffer around Orweb&Orbot.
> 
> But the Android device isn't a gateway, unless you're tethering? If you
> mean only applications with native Tor support should be let through,
> that's the "access:fenced" option. Setting it up for all of the main
> device user account is literally that as one line, "access:fenced". Or
> for just a specific app, it's "access:fenced app:com.example.foo":

We could definitely implement this for the Orbot VPN via the tun2socks
code... essentially drop all traffic that is not connected to the local
Tor SOCKS or HTTP ports. We are also considering a little-snitch style
interactive mode that prompts the user based on hostnames and ports, to
approve each connection.

+n
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

