Delivery-Date: Mon, 03 Nov 2014 01:18:51 -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 E6A731E050E;
	Mon,  3 Nov 2014 01:18:49 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 09B1B31661;
	Mon,  3 Nov 2014 06:18:45 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C60D83165D
 for <tor-talk@lists.torproject.org>; Mon,  3 Nov 2014 06:18:41 +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 jHRro0VFl225 for <tor-talk@lists.torproject.org>;
 Mon,  3 Nov 2014 06:18:41 +0000 (UTC)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com
 [IPv6:2a00:1450:4010:c04::234])
 (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 72BE830F0C
 for <tor-talk@lists.torproject.org>; Mon,  3 Nov 2014 06:18:41 +0000 (UTC)
Received: by mail-lb0-f180.google.com with SMTP id u10so321028lbd.25
 for <tor-talk@lists.torproject.org>; Sun, 02 Nov 2014 22:18:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=Uk3378qYtlG6sGtmC9MFzPVId3QNFTWwT10HD3PIuAs=;
 b=WdkpXr6AsMUvz65nNKOglRUciMb54ONmu6yr91C5WQnGruKzPZSakxENWfzV+NB1pW
 YI+qNOd955XZcmLg/erSEhYhKQw8T81BylDve7ThyJ0b+9G3noZVELgDwmLPtOovzwaY
 hs3/P873wfa7GN93MRN6P9vDHlyybTGkBjvMsVVGNDKyMdPUEQ86m4YnMhfUMmPusajy
 WXpu9kkWQ56BjrYFbad2KgB4xy9ZETZi+MSH5JKr2jtP0LyImNxUiW2nk6tsyPsWkvtm
 g6IBckPu//uM5Exw/gU7SR88f8X3E7eTpVYpBulSe80ZGdrfuL2gmEyyrCCm4TYLSRL6
 wPsQ==
MIME-Version: 1.0
X-Received: by 10.112.169.106 with SMTP id ad10mr48250973lbc.13.1414995518254; 
 Sun, 02 Nov 2014 22:18:38 -0800 (PST)
Received: by 10.112.156.225 with HTTP; Sun, 2 Nov 2014 22:18:37 -0800 (PST)
In-Reply-To: <1943762.342hlgev77@ncpws04>
References: <7488606.2oxgLGVBPl@ncpws04>
 <CAJVRA1QJ26Vtjt57N4Ducw3LV=MxnqaoGj0DY6L2D4-5vq8rxw@mail.gmail.com>
 <1943762.342hlgev77@ncpws04>
Date: Sun, 2 Nov 2014 22:18:37 -0800
Message-ID: <CAJVRA1SvtJ8-Vpz3RPqnQEjG-XMuTMoYpNigDeUso8=piS_bVA@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: 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>

On 11/2/14, Lars Boegild Thomsen <lth@reclaim-your-privacy.com> 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.

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 :)


best regards,
-- 
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

