Delivery-Date: Fri, 07 Nov 2014 11:29:37 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	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 F0AE01E0AE2;
	Fri,  7 Nov 2014 11:29:35 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0C6643174A;
	Fri,  7 Nov 2014 16:29:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 6E9353171C
 for <tor-talk@lists.torproject.org>; Fri,  7 Nov 2014 16:29:27 +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 Eae15zL3eua2 for <tor-talk@lists.torproject.org>;
 Fri,  7 Nov 2014 16:29:27 +0000 (UTC)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com
 [IPv6:2a00:1450:400c:c00::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 2169D313D7
 for <tor-talk@lists.torproject.org>; Fri,  7 Nov 2014 16:29:27 +0000 (UTC)
Received: by mail-wg0-f45.google.com with SMTP id x12so4156172wgg.32
 for <tor-talk@lists.torproject.org>; Fri, 07 Nov 2014 08:29:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=tGX/klXwVh5OJIah2CvbBbAqGqB72kRij5pLVAY0ts8=;
 b=olXV/aIpwp/PbFyjBqzigDLe2GvjwDWGLGdrxQR39hZLhwTrXmmi2ccnRqhfn9kilO
 rRRlszeac7IAL7P0BM6qZ1upZ2vDZLqK6Sk0FjKZDci4NRzX1mmh90A3AzYLRSwiZz+F
 q721CnTVLLIiNdf+esfzrOUQnpqVZISRAZ+Xyygp/Rg0qXRPICByO4jvrI0iR86gifDI
 rU/A3wMHuTXMPlLpY4RBtCNW/RZ+Jld8ki4Y7Fkdqnu9l4ja8WBoKW8B6WvFuDl5TVbx
 /5AzNsrLpq2WOmMwjIO+Fq40fzHeXVNMqUlwGoPWzdZpskWWV29gyJHu6wtRjZZAbHZ3
 byrA==
X-Received: by 10.181.13.20 with SMTP id eu20mr6569508wid.36.1415377764177;
 Fri, 07 Nov 2014 08:29:24 -0800 (PST)
Received: from [192.168.1.11] (ANice-652-1-324-82.w86-193.abo.wanadoo.fr.
 [86.193.107.82])
 by mx.google.com with ESMTPSA id n4sm12339982wjb.40.2014.11.07.08.29.22
 for <tor-talk@lists.torproject.org>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Fri, 07 Nov 2014 08:29:23 -0800 (PST)
Message-ID: <545CF363.7020201@gmail.com>
Date: Fri, 07 Nov 2014 17:29:23 +0100
From: Aymeric Vitte <vitteaymeric@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <7488606.2oxgLGVBPl@ncpws04> <8791008.gPgc6LIrom@ncpws04>
 <CAJVRA1THJ5urkXWVe7UgKVy5gA=1a6yQ4F1_=1v3m4Yu-pgxJw@mail.gmail.com>
 <3413830.AxW13VOK2Y@ncpws04>
In-Reply-To: <3413830.AxW13VOK2Y@ncpws04>
Subject: Re: [tor-talk] Cloak Tor Router
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

And 5 "do not send anything outside", no? Usually you can restrict with =

your ISP box but can you trust it?

What happens if you connect directly your PC to the Cloak with a cable?

Maybe the concept of several wifis is good but I don't see it very =

usable, not sure what would be the security requirements for this but =

assuming that I am trusting my local network why not a simple web =

interface where you can configure the same for any device connected to =

the box:

- do not allow anything outside
- allow all traffic outside Tor
- force everything through Tor (warning: close your bittorrent clients)
option: the Cloak could detect the bittorrent traffic
- force eveything through Tor except torrents
- force ssl through Tor, non ssl outside
...

Regards,


Le 05/11/2014 05:19, Lars Boegild Thomsen a =E9crit :
> On Sunday 02 November 2014 00:47:40 coderman wrote:
>> even a simple one time, "You are about to route your traffic over the
>> Tor network. Turn off your torrents and don't upgrade poorly written
>> applications".
>>
>> the zero guidance to unsuspecting is what i am most concerned about;
>> even basic captive portal warning would be a benefit.
> I will definitely look into this one.  This should be quite easy to imple=
ment by messing a bit with the firewall tables :)
>
> Only problem I see is that to make it useful I think it would have to tim=
e out at some point.  One example I have bought up a few times is my cheap =
and rather chatty media player.  I have not dug into the details exactly bu=
t I _know_ it "phones home" regularly and it is definitely a use case where=
 the Tor browser bundle would be impossible.  Problem is that one is unatte=
nded so if I were to do a captive portal kind of page and that would requir=
e a positive acceptance, the Cloak would be useless for this scenario.
>
> Number of wireless networks are not an issue so I _am_ beginning to think=
 that more than two is necessary.  For example:
>
> 1. Open - Open network - no Tor
> 2. Transparent proxy - all tcp traffic allowed - forced through Tor - eve=
rything on separate circuits  - captive warning
> 3. Transparent proxy as 2 minus captive portal (for gadgets or someone wh=
o know what they are doing)
> 4. Isolating proxy - only https allowed - forced through Tor - everything=
 on separate circuits and everything else blocked
>
> It is not really a problem to make more than two so if this makes the Clo=
ak more flexible I'd say it's the way to go.
>

-- =

Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms

-- =

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

