Delivery-Date: Wed, 03 Sep 2014 22:14:29 -0400
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,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 E7BDE1E0E6A;
	Wed,  3 Sep 2014 22:14:26 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3912A23A87;
	Thu,  4 Sep 2014 02:14:23 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 551A2236C2
 for <tor-talk@lists.torproject.org>; Thu,  4 Sep 2014 02:14:19 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 rOLxgWXAjc1w for <tor-talk@lists.torproject.org>;
 Thu,  4 Sep 2014 02:14:19 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 2FA1222930
 for <tor-talk@lists.torproject.org>; Thu,  4 Sep 2014 02:14:19 +0000 (UTC)
Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified))
 by mx1.riseup.net (Postfix) with ESMTPS id 6E33E53D9D
 for <tor-talk@lists.torproject.org>; Wed,  3 Sep 2014 19:14:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1409796856; bh=J0wCiyrjQPYW4khQNVoBiZoj2nNYFzIjymnVwZWmRbM=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=czbEC+HAB+jiSFo6xznmD99JE+Koua8G5wDI3pEm12QFwW0MWGKlCBN10hX4gUGjS
 Zm/ALKdn7J/EK7O3AhDJCNkcgP1BFfZ9C7NdIifRGG9aNKTASQ4BhQdILh8dBfYg8p
 qjbCT33PiSngW3KPhpfJ6rRlSfPZIDHqleh3tkHw=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id 9F85A42B1D
Message-ID: <5407CAF4.5070901@riseup.net>
Date: Wed, 03 Sep 2014 20:14:12 -0600
From: Mirimir <mirimir@riseup.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <453f2ed0b4289906729ebd68b697af95@autistici.org>
In-Reply-To: <453f2ed0b4289906729ebd68b697af95@autistici.org>
X-Virus-Scanned: clamav-milter 0.98.4 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] Each TCP stream a new circuit?
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="windows-1252"
Content-Transfer-Encoding: quoted-printable
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 09/03/2014 08:50 AM, spriver wrote:
> Hi,
> is there any possibility to divide up each TCP connection into a single
> tor circuit? What would be the effect on the usability of Tor?
> =

> Or is it a complete nonsense?
> =

> Cheers
> =

> spriver

Check out these options in the Tor manual:

IsolateClientProtocol

Don=92t share circuits with streams using a different protocol. (SOCKS 4,
SOCKS 5, TransPort connections, NATDPort connections, and DNSPort
requests are all considered to be different protocols.)

IsolateDestPort

Don=92t share circuits with streams targetting a different destination port.

IsolateDestAddr

Don=92t share circuits with streams targetting a different destination
address.

-- =

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

