Delivery-Date: Thu, 24 Jul 2014 11:27:14 -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.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	FROM_LOCAL_NOVOWEL,RCVD_IN_DNSWL_MED,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 84FCA1E0A99
	for <archiver@seul.org>; Thu, 24 Jul 2014 11:27:12 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 798AE2F1E8;
	Thu, 24 Jul 2014 15:27:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 8B2A22E71C
 for <tor-talk@lists.torproject.org>; Thu, 24 Jul 2014 15:14:13 +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 ZR9ucYZpLUY3 for <tor-talk@lists.torproject.org>;
 Thu, 24 Jul 2014 15:14:13 +0000 (UTC)
Received: from mout.gmx.com (mout.gmx.com [74.208.4.200])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 67ECE2E71A
 for <tor-talk@lists.torproject.org>; Thu, 24 Jul 2014 15:14:13 +0000 (UTC)
Received: from [127.0.0.1] ([99.190.181.188]) by mail.gmx.com (mrgmxus001)
 with ESMTPSA (Nemesis) id 0M4Gij-1WK1343X9f-00rmhF for
 <tor-talk@lists.torproject.org>; Thu, 24 Jul 2014 17:14:10 +0200
Message-ID: <53D12294.2040900@gmx.com>
Date: Thu, 24 Jul 2014 10:13:24 -0500
From: Joe Btfsplk <joebtfsplk@gmx.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <53CE494A.90002@bitmessage.ch> <53CF68FB.80105@torproject.org>
 <53CFFB16.1040701@gmx.com> <53D0CAC5.2040305@torproject.org>
In-Reply-To: <53D0CAC5.2040305@torproject.org>
X-Provags-ID: V03:K0:gqxJmJLjm5moihnfqqLTd0wcAnMMCmnVfa8whGFkUBnph/dQQpE
 pa86CDnKc5U3OMQ3MoxXaBGXVIFYu6bd3Nu/fMMkUrJlR442EHHLuakKoxt8dIP9Ynx6IMV
 UM7lCLKU9jy0mr/gZzngCeY0DTZ/tIVggs7OMltxfc3nEV1hAJp0gpBd0v7cxMv/CC5VFKS
 13RVokjBPxrLrFJsGgQ0A==
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Tor Browser window size
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 7/24/2014 3:58 AM, Georg Koppen wrote:
> Joe Btfsplk:
>>
>> Should TBB always start in partial window size?
> It depends on your available screen size. But in almost all cases, yes,
> TBB should always start in partial window size at least until we find a
> good way to deal with maximized browser windows (see e.g.:
> https://bugs.torproject.org/7256).
Thanks Georg,
Clearly I've forgotten or never knew why (partial) TBB window sizes can 
be spoofed, but standard multiples for maximized TBB windows *can't* be 
spoofed, instead.

? Don't a "majority" of users maximize something like browsers, for 
general use?  I've never seen it mentioned that most users leave TBB in 
partial screen.
I wouldn't think TBB (window size) would be used differently than 
regular browsers (a result of human habit).

I rarely see people using browsers in partial size, unless doing some 
between app operation / comparison.  I'm talking about what the masses do.
>> Vanilla Firefox starts in maximized mode, if that was the state when
>> closed (I think).
>> TBB always starts in partial screen mode, even if last closed while in
>> full screen.  Many apps remember the last screen size.
>> Is there an anonymity reason to have TBB  start in partial screen?
> Not per se, but see https://bugs.torproject.org/7256 for the issue that
> still needs to get solved first.
>
I don't understand your last statement in relation to the bug you linked:
>
> Right now, we set the size of new Tor Browser windows such that their 
> content area is a 200x100 multiple. We also lie to content that the 
> entire desktop resolution is this size.
>
> However, this potentially leaks information for users who maximize 
> their browser windows, as such windows will no longer be rounded.
There, Mike P. is clearly saying that maximizing TBB window poses a 
threat (under the right circumstances).  Am I misunderstanding it?
But, I'm unclear on which sentence (current TBB behavior) causes 
potential info leak, *IF users maximize* TBB:
The 1st sentence, "... content area is a 200x100...", or the 2nd one, 
"We also lie...."  Or, both?
-- 
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

