Delivery-Date: Fri, 25 Mar 2016 07:22:51 -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,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 5822B1E0456;
	Fri, 25 Mar 2016 07:22:49 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3A4A13927F;
	Fri, 25 Mar 2016 11:22:45 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 655D53939F
 for <tor-talk@lists.torproject.org>; Fri, 25 Mar 2016 11:22: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 61kDIIPX-lGN for <tor-talk@lists.torproject.org>;
 Fri, 25 Mar 2016 11:22:41 +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 "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 363A239281
 for <tor-talk@lists.torproject.org>; Fri, 25 Mar 2016 11:22:41 +0000 (UTC)
Received: from cotinga.riseup.net (unknown [10.0.1.164])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 729FB1A14B9
 for <tor-talk@lists.torproject.org>; Fri, 25 Mar 2016 11:22:38 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1458904958; bh=HnepEvSEy4pA5icjYL5KTjINXTeaDsMY9aVxOdUF6TA=;
 h=In-Reply-To:References:Subject:From:Date:To:From;
 b=kh1PWrfcFgYy3zRvsf5nF/xwkdHGxPx0W+aQk0C9AWg9TWOQmAXMjQY0U/AV6avNK
 JJCtlWJhXpGrUCcAktXrLVEXo1BghitE4xB9Uz7+jHRuld23xCrXm1KWwCbuEKAkhn
 +GMJ3yNrpwXPK7bViDXNMigMCWNmeIR0X+oF17Pk=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: flipchan) with ESMTPSA id B62E94114B
In-Reply-To: <194344.4560.bm@smtp117.mail.ir2.yahoo.com>
References: <194344.4560.bm@smtp117.mail.ir2.yahoo.com>
MIME-Version: 1.0
From: Flipchan <flipchan@riseup.net>
Date: Fri, 25 Mar 2016 12:22:34 +0100
To: tor-talk@lists.torproject.org
Message-ID: <5FB50D79-FB7D-4134-B7F1-0472A1534175@riseup.net>
X-Virus-Scanned: clamav-milter 0.99 at mx1.riseup.net
X-Virus-Status: Clean
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>

I think roundcube(an email client) works with easy session and switchin your IP shoulnd effect that session

Ben Stover <bxstover@yahoo.co.uk> skrev: (25 mars 2016 12:12:07 CET)
>Hello Paul (and others),
>
>the problem is for example when I login into a remote mailbox through
>TorBrowser then the mail box provider
>see my IP (=IP of ExitNode).
>
>Since I often stay longer than 10 minutes in my remote mailbox an IP
>switch happens during my mailbox login session.
>Unfortunately a lot of mailbox provider setup smart "security session
>procedures".
>As soon as they detect an IP switch they force the user to re-login
>again (at minimum).
>
>Even worse: Some mail providers consider an account and password break
>and force the user to "verify" that
>they are really to owner of the account with a long-winded confirmation
>procedure.
>This could happen when only changing the country as well.
>Very annoying.
>
>So the easiest way to prevent these situation would be to keep the
>current Tor circuit (or at least the ExitNode).
>
>From what I read so far a "keep-circuit-instruction" is currently not
>possible.
>
>Why not offering the user such a (torrc) option? So its up to him if he
>wants an extended circuit-session-time or not.
>
>Ben
>
>>I'm confused. What is the situation you are concerned about?  A new
>>stream would go over a new circuit whether the previous stream is kept
>>alive or not. Is that not so? And I'm not sure what keeping the idle
>>stream open has to do with this. I understand the UX issues of
>>switching circuits, and I get the threat if not allowing a stream to
>>close causes attaching indefinitely to new circuits.  But I don't
>>understand why it is bad to have a new stream open on a new circuit
>>after another stream closes that was artificially kept open for a
>>while vs. having the new stream open after an initial stream closed
>>normally.
>
>>aloha,
>>Paul
>
>
>
>
>
>-- 
>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

-- 
Sincerly Flipchan
-- 
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

