Delivery-Date: Tue, 22 Mar 2016 21:11:36 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_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 068D41E0E0D;
	Tue, 22 Mar 2016 21:11:34 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id CB01D3928B;
	Wed, 23 Mar 2016 01:11:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 41AE83928B
 for <tor-talk@lists.torproject.org>; Wed, 23 Mar 2016 01:11:26 +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 wpsecaYDmGT4 for <tor-talk@lists.torproject.org>;
 Wed, 23 Mar 2016 01:11:26 +0000 (UTC)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com
 [IPv6:2607:f8b0:400c:c05::22b])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 0FBE23927E
 for <tor-talk@lists.torproject.org>; Wed, 23 Mar 2016 01:11:25 +0000 (UTC)
Received: by mail-vk0-x22b.google.com with SMTP id e185so1244955vkb.1
 for <tor-talk@lists.torproject.org>; Tue, 22 Mar 2016 18:11:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=nsuchy-top.20150623.gappssmtp.com; s=20150623;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
 bh=dORgmmeNgQbFHA0xgqz3ldHBKMZu+cSPYzNdOtgu2HI=;
 b=laNR0cbhunjwKDpDBid5z7tZl4pl+bDUOch2mocrVryceDresqGnc9dfVD7g/OoQOc
 uD1NFXYO6leHVO9CDrYJBvxggoLtOVTUMwEGaTO3KVrHBw/LwBVUdZKbfUGqjI8R7bPP
 5jo2nhg/d32GW8xROZaqZKgKNvYHkBt7QGop3MTSrE0E24x2N9kkxWHm2ZjrCyL7U6/J
 5hI5M0idKWaaaQMsXwo2xmP591qzgvowFs1Rv7BUehXxPhrBsq6CSv1OvkPVTR17Oxuy
 ph3HdpZ+wqZkX/RfOzoT9sLeoYXaeUxsBGcPVPyl3FM+a7D7bW/5K5WKU4y1MIlO44r5
 g0vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to;
 bh=dORgmmeNgQbFHA0xgqz3ldHBKMZu+cSPYzNdOtgu2HI=;
 b=m33CePeQvLI2RKXIxraRV/CfdUHo5PJ6KaZI1rYxD84J1Gm7ExR/YtiRS3fHLgpa2v
 Tw6NP5pII8Oe9Nfjeru1i00r3h9yO1nXUb59v0PZG+ULsR+uy/yRv7yTAYYpr9JNueP6
 nwn8OIPwD9xbvM08FnlBjJKFjeVqmCtnjY4rfp04t0zYjnVk+Eae0EvkIZu8hgPxGozE
 5b4D399uc9znQZ0WabDQgFzjyIJ+LlscnG1wo6wrbWWNLT8xG+mXrqUanqfsKyOGlesj
 w53OekWaxjtxauQ08Q6JoZKZQK3EkKOnY0tEXNQt2YaH1tzTAC8Buq1ufk/wpHCkVHtJ
 uVcQ==
X-Gm-Message-State: AD7BkJKUPqq9jqYY5A3icQ/k7oNZ2k2L5eoCEsNsH/wRWsxnIfOfhm6uoKFPtPnkJ1j3703erOyPvvVROb234dSs
X-Received: by 10.176.2.231 with SMTP id 94mr80170uah.106.1458695482251; Tue,
 22 Mar 2016 18:11:22 -0700 (PDT)
MIME-Version: 1.0
References: <259387.67882.bm@smtp146.mail.ir2.yahoo.com>
 <20160323000835.GJ15350@torproject.org>
In-Reply-To: <20160323000835.GJ15350@torproject.org>
From: Nathaniel Suchy <admin@nsuchy.top>
Date: Wed, 23 Mar 2016 01:11:12 +0000
Message-ID: <CAD--ZDVW5jEXizN-6DQ3y6OYam6z36NLPuhSeQv7RECJG8YLHA@mail.gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Extend auto-IP-switching-time in TorBrowser (and
 depending from time of inactivity)
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>

Well now you said that publicly if we told you and you did it government
agents could add up 30 minute ip sessions to you and harm your anonymity.
On Tue, Mar 22, 2016 at 8:08 PM Mike Perry <mikeperry@torproject.org> wrote:

> Ben Stover:
> > As far as I know TorBrowser switches automatically every 10 minutes the
> node chain resp. the IP of the ExitNode.
> >
> > Can I somehow extend this timeout time to another value e.g. 30 minutes?
> >
> > Or (even better) can I let Tor auto-switch the IP and chain depending
> from the time of inactivity (.e.g when 15 minutes no
> > web page is called)?
>
> We had a long discussion about this in
> https://trac.torproject.org/projects/tor/ticket/15482. Ultimately, a fix
> was merged to Tor, but it did not cause Tor to update its circuit
> discard timeout (the "dirtyness" timeout) upon stream detach.
>
> I have also noticed worse behavior since Tor Browser switched from the
> patch I
> wrote in
>
> https://trac.torproject.org/projects/tor/attachment/ticket/15482/0001-Bug-15482-Don-t-abandon-circuits-that-are-still-in-u.patch
> to the version in Tor today.
>
> I also agree we should be more aggressive about keeping circuits in use.
> I think we should go back to updating this timeout when streams are
> closed, otherwise we risk the situation where HTTP KeepAlive keeps an
> idle stream open for several minutes, and then when that stream closes,
> it is more likely that a new stream will go on a separate circuit
> because the timeout expired while the stream was open but idle.
>
> This situation will only get worse if/when we enable HTTP 2.
>
> I have noticed websites switching language on me mid-use as a result.
> This is extremely bad for usability, and makes no sense for privacy on
> the web, since web sessions contain plenty of identifying information
> when they resume, regardless of what circuit they use. In my
> not-so-humble opinion here, the Tor network usage should match Tor
> Browser's identifier protections exactly. Any mismatch is just bad
> usability for no privacy gain...
>
>
> --
> Mike Perry
> --
> 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
>
-- 
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

