Delivery-Date: Mon, 02 Jun 2014 15:56:25 -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 moria.seul.org (Postfix) with ESMTPS id 6982E1E0943
	for <archiver@seul.org>; Mon,  2 Jun 2014 15:56:23 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id BB3B62F540;
	Mon,  2 Jun 2014 19:56:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B28CD2F4BA
 for <tor-talk@lists.torproject.org>; Mon,  2 Jun 2014 19:46:16 +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 zKT6c8SJLuHH for <tor-talk@lists.torproject.org>;
 Mon,  2 Jun 2014 19:46:16 +0000 (UTC)
Received: from mout.gmx.com (mout.gmx.com [74.208.4.200])
 (using TLSv1.2 with cipher DHE-RSA-AES256-SHA256 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 980942F4B2
 for <tor-talk@lists.torproject.org>; Mon,  2 Jun 2014 19:46:16 +0000 (UTC)
Received: from [127.0.0.1] ([99.190.181.188]) by mail.gmx.com (mrgmxus001)
 with ESMTPSA (Nemesis) id 0M3ikx-1Wa1Mi3hD7-00rFtj for
 <tor-talk@lists.torproject.org>; Mon, 02 Jun 2014 21:46:14 +0200
Message-ID: <538CD474.1090509@gmx.com>
Date: Mon, 02 Jun 2014 14:45:56 -0500
From: Joe Btfsplk <joebtfsplk@gmx.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <CAD2Ti29ds-CxA9OBWZdWx0JOen4mhyG5-JFWOLJ5tcLX7tkXHw@mail.gmail.com>
 <5387EF98.600@riseup.net> <20140530071155.GA9865@glue.grepular.com>
 <5388966F.4040603@gmx.com> <20140530175831.GA1750@glue.grepular.com>
 <5388E145.8010707@gmx.com> <20140530203627.GA7497@glue.grepular.com>
 <538B739C.9040301@gmail.com> <20140602204908.759105bd@mint-N130>
In-Reply-To: <20140602204908.759105bd@mint-N130>
X-Provags-ID: V03:K0:/5j0l+Wvt35l4XdQnzLvzLuz7Myl23ndvV+RO8rXiJWWmbI8ulW
 rNbrqFgR0tB9NqnZHOPVcvsdyJyibcTMUV951NPJey0LMVHXBGdy/xyjEaoh3lx9293tXXD
 uymV4hvAgTTT31ULCAJY6QZtDO8gmks0AJNcn08GXvLBFIr4RkWkYo4CLj0hLjm9htrvYjV
 0QwiMCV6FatH3BvzRQLQQ==
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] [OT[ New web-cookie policies on internet
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 6/2/2014 1:49 PM, SecTech wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> The TBB with TorButton has the ability to delete all cookies.
> Than the site can't track you, but you can enable first party cookies.
>
> SecTech
>
AFAIK, Torbutton doesn't have the ability to delete 1st party cookies, 
as soon as the tab containing the given 1st party / temporary cookies is 
closed.
I understood it cleared all data from sites upon closing TBB or getting 
a new identity (if any is allowed to be stored during sessions).

Now, how much tracking between sites could be done w/ 1st party 
cookies?  Not sure.  There are different kinds of "tracking."
Maybe depend if entity setting them is "following the rules."
Normally, we think of "tracking" as 3rd party cookies or web beacons, etc.

But what about if 2 seemingly unrelated sites are run by the same person?
Is there anything *absolutely* preventing an operator from reading 
cookies between sites he owns?  At least, be able to recognize cookies 
he set on other sites?
-- 
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

