Delivery-Date: Mon, 03 Nov 2014 02:26: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_SIGNED,
	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 C3C311E004F;
	Mon,  3 Nov 2014 02:26:35 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DFC41315C9;
	Mon,  3 Nov 2014 07:26:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2FFC531064
 for <tor-talk@lists.torproject.org>; Mon,  3 Nov 2014 07:26:28 +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 3_sc21I4S55i for <tor-talk@lists.torproject.org>;
 Mon,  3 Nov 2014 07:26:28 +0000 (UTC)
Received: from s2.netcompartner.com
 (lbthomsen-3-pt.tunnel.tserv6.fra1.ipv6.he.net [IPv6:2001:470:1f0a:10f2::2])
 by eugeni.torproject.org (Postfix) with ESMTP id F354325C1A
 for <tor-talk@lists.torproject.org>; Mon,  3 Nov 2014 07:26:27 +0000 (UTC)
Received: from ncpws04.localnet (ncpws04.netcompartner.com
 [IPv6:2001:470:ec48:0:e2cb:4eff:fe3e:11c6])
 by s2.netcompartner.com (Postfix) with ESMTPSA id 261B5C0536;
 Mon,  3 Nov 2014 08:26:25 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
 d=reclaim-your-privacy.com; s=2014; t=1414999585;
 bh=6eSh854F9qZGXQm73GsJ1Psjz5KROInmkhSqGAfAAkI=;
 h=From:To:Cc:Subject:Date:In-Reply-To:References:From;
 b=fJooX7GDx41udc6UUQjAZuCUjbtQWb5G7jlmW3ECrrxeNcn6e7ywvfoELPZMvtMmj
 WvC+tvLBdVVzX2pmx6xFNp875vL2vbGJrDx8PaBxnONwjKvSHNM26rJc1P4tGKXiN+
 1UE6ByNY7D7s1EBpGB5t5AhcAeoONM8yZfPWaTStW+3aCuPWjN1obfM7R5HVNPcI/m
 qtjEId3s/oBJBsKrZoUsVddB3eW966lN3YmH30cNwIYqkPFlwfatl7GCVLh2GBx3is
 lCiR3ZejvvX8yyf0qvgvGUGGwZOHw3q7KXRUQgGPjnikCkeizq7y1TQuCGmifSc62z
 ObK/b+RnUewbA==
From: Lars Boegild Thomsen <lth@reclaim-your-privacy.com>
To: tor-talk@lists.torproject.org
Date: Mon, 03 Nov 2014 15:26:21 +0800
Message-ID: <2183030.0TfTSMp6Az@ncpws04>
Organization: Reclaim Your Privacy
User-Agent: KMail/4.14.1 (Linux/3.16-3-amd64; KDE/4.14.1; x86_64; ; )
In-Reply-To: <CAJVRA1SvtJ8-Vpz3RPqnQEjG-XMuTMoYpNigDeUso8=piS_bVA@mail.gmail.com>
References: <7488606.2oxgLGVBPl@ncpws04> <1943762.342hlgev77@ncpws04>
 <CAJVRA1SvtJ8-Vpz3RPqnQEjG-XMuTMoYpNigDeUso8=piS_bVA@mail.gmail.com>
MIME-Version: 1.0
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>

On Sunday 02 November 2014 22:18:37 coderman wrote:
> > I just tried with the current Cloak build.  And different clients use
> > different circuits.  However, none of the configuration options appear to
> > work, so I reckon it is down to:
> if each client has a a distinct address (not behind NAT) this works
> fine.  ideally there would be a way to force this behavior on each
> connection so that clients behind NAT get stream isolation even for
> connections to the same destinations.

In the case of a standard Cloak (as least as it is envisioned right now) that is not a problem for Cloak then.  Cloak _will_ be the Wireless Access Point, it will enforce client isolation at Wi-Fi level and it will hand out separate address to each client.

Hey - one challenge down :)

> as for which options your build supports, that's a good question.  i'm
> not sure best to determine from a given Tor binary what options it
> supports based on version and build configuration...  (maybe someone
> on list knows off hand?  i can check later :)

I think that was explained in another message already.

-- 
Lars Boegild Thomsen
https://reclaim-your-privacy.com
Jabber/XMPP: lth@reclaim-your-privacy.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

