Delivery-Date: Sun, 02 Nov 2014 05:53:24 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD 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 7D7F11E0420;
	Sun,  2 Nov 2014 05:53:22 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E04293168A;
	Sun,  2 Nov 2014 10:52:56 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 075AB315D4
 for <tor-talk@lists.torproject.org>; Sun,  2 Nov 2014 10:52:50 +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 4oPg8S2uTlWV for <tor-talk@lists.torproject.org>;
 Sun,  2 Nov 2014 10:52:49 +0000 (UTC)
X-Greylist: delayed 990 seconds by postgrey-1.34 at eugeni;
 Sun, 02 Nov 2014 10:52:49 UTC
Received: from michaelblizek.twilightparadox.com
 (michaelblizek.twilightparadox.com [193.238.157.55])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id C86B230EFD
 for <tor-talk@lists.torproject.org>; Sun,  2 Nov 2014 10:52:49 +0000 (UTC)
Received: from localhost ([127.0.0.1] helo=grml)
 by michaelblizek.twilightparadox.com with esmtp (Exim 4.72)
 (envelope-from <michi1@michaelblizek.twilightparadox.com>)
 id 1XksW7-0005T1-Qz; Sun, 02 Nov 2014 11:36:16 +0100
Date: Sun, 2 Nov 2014 11:36:14 +0100
From: michi1@michaelblizek.twilightparadox.com
To: Lars Boegild Thomsen <lth@reclaim-your-privacy.com>
Message-ID: <20141102103614.GA5323@grml>
References: <7488606.2oxgLGVBPl@ncpws04>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <7488606.2oxgLGVBPl@ncpws04>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: tor-talk@lists.torproject.org
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-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>

Hi!

On 17:09 Sat 01 Nov     , Lars Boegild Thomsen wrote:
> and we really would like this product to be what the TorRouter never became

I would really like to see this happen. To me it seems your goals are
slightly different tough. Torouter tries to provide public wifi (without
risks for the operator), run bridge (and other) nodes and create hidden
services (see https://trac.torproject.org/projects/tor/wiki/doc/Torouter ).
The kickstarter page suggests it can be used to anonymise outgoing traffic
from clients to the internet. This may be quite problematic for these reasons:

1) People will not get hardened clients. See
https://www.torproject.org/projects/torbrowser/design/ for a list of changes
made by torproject.

2) Every device can sniff on traffic from all other devices on the same
network. If you have one device which is compromised or somebody breaks the
wifi securety you are in trouble.

3) Depending on the configuration you may end up routing traffic from multiple
devices over the same circuit. You will almost certainly route traffic from
different programs on the same device over the same circuit. This may allow an
exit node operator to correlate multiple identities.

4) If you have a mobile device you probably want to be safe everywhere, not
just at home.

BTW: If you want to show people you are serious about privacy I would suggest
creating your screenshots+demos with a free operating system.

	-Michi
-- 
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
-- 
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

