Delivery-Date: Tue, 29 Jul 2014 09:42:05 -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.9 required=5.0 tests=BAYES_00,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 3D2151E0A15
	for <archiver@seul.org>; Tue, 29 Jul 2014 09:42:03 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A89943025A;
	Tue, 29 Jul 2014 13:42:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C168E306FE
 for <tor-talk@lists.torproject.org>; Tue, 29 Jul 2014 13:29:55 +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 2lkCU20K6WDI for <tor-talk@lists.torproject.org>;
 Tue, 29 Jul 2014 13:29:55 +0000 (UTC)
Received: from srv-ch-mail.apawc.com.au (203-206-130-18.perm.iinet.net.au
 [203.206.130.18])
 by eugeni.torproject.org (Postfix) with ESMTP id 5D5F12FF2B
 for <tor-talk@lists.torproject.org>; Tue, 29 Jul 2014 13:29:55 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1])
 by srv-ch-mail.apawc.com.au (Postfix) with ESMTP id 5BA6DAA81C2
 for <tor-talk@lists.torproject.org>; Tue, 29 Jul 2014 09:29:52 -0400 (EDT)
Received: from srv-ch-mail.apawc.com.au ([127.0.0.1])
 by localhost (srv-ch-mail.apawc.com.au [127.0.0.1]) (amavisd-new, port 10032)
 with ESMTP id vRsb9-4UwPT5 for <tor-talk@lists.torproject.org>;
 Tue, 29 Jul 2014 09:29:52 -0400 (EDT)
Received: from localhost (localhost.localdomain [127.0.0.1])
 by srv-ch-mail.apawc.com.au (Postfix) with ESMTP id F1974AA81C8
 for <tor-talk@lists.torproject.org>; Tue, 29 Jul 2014 09:29:51 -0400 (EDT)
X-Virus-Scanned: amavisd-new at apawc.com.au
Received: from srv-ch-mail.apawc.com.au ([127.0.0.1])
 by localhost (srv-ch-mail.apawc.com.au [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id 7zD0TOxR0kUJ for <tor-talk@lists.torproject.org>;
 Tue, 29 Jul 2014 09:29:51 -0400 (EDT)
Received: from srv-ch-mail.apawc.com.au (srv-ch-mail.apawc.com.au
 [192.168.0.16])
 by srv-ch-mail.apawc.com.au (Postfix) with ESMTP id DDC38AA81C2
 for <tor-talk@lists.torproject.org>; Tue, 29 Jul 2014 09:29:51 -0400 (EDT)
Date: Tue, 29 Jul 2014 13:29:51 +0000 (UTC)
From: Paul Templeton <paul@apawc.com.au>
To: tor-talk@lists.torproject.org
Message-ID: <1877401614.7764.1406640591875.JavaMail.zimbra@apawc.com.au>
MIME-Version: 1.0
X-Originating-IP: [58.6.49.128]
X-Mailer: Zimbra 8.0.4_GA_5737 (ZimbraWebClient - FF31 (Win)/8.0.4_GA_5737)
Thread-Topic: Spoofing a browser profile to prevent fingerprinting
Thread-Index: A2XGGBCJsVu/4LqOUu9AYpplQKHPPg==
Subject: [tor-talk] Spoofing a browser profile to prevent fingerprinting
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>

Fingerprinting is becoming herder to circumvent an new tactics added all the time you really need a way to remove your system from the equation.

The simplest way would be to add a VE service on a TOR relay publishing a browser. You would not only be asking TOR relay providers to donate some bandwidth but also some processing power. TOR users connect to a VE via a client to get to a browser and if there is any fingerprinting it just on the relay - nothing is stored on the users system. The VE would destroy the session one disconnected. Being a VE environment you could use all the normal tools of balance loading and migrating of running sessions across the TOR network. Down side would be whether or not the existing network could cope with data streaming.

One day when I have time I might build a VE environment and experiment such a concept.

Warm Regards

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

