Delivery-Date: Thu, 31 Jul 2014 21:44:33 -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 F30C31E0BD4;
	Thu, 31 Jul 2014 21:44:31 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id BFA5430B14;
	Fri,  1 Aug 2014 01:44:27 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id BC0AD30ABC
 for <tor-talk@lists.torproject.org>; Fri,  1 Aug 2014 01:44:24 +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 uPPdAL3SnO6x for <tor-talk@lists.torproject.org>;
 Fri,  1 Aug 2014 01:44:24 +0000 (UTC)
Received: from jessica.everdot.org (unknown [IPv6:2001:470:1f0b:1c12::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 8DF91309A5
 for <tor-talk@lists.torproject.org>; Fri,  1 Aug 2014 01:44:24 +0000 (UTC)
Received: from mail.everdot.org (primail.everdot.org [IPv6:2001:470:dc2e:5::2])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by jessica.everdot.org (Postfix) with ESMTPS id 4A7D0FA0203
 for <tor-talk@lists.torproject.org>; Fri,  1 Aug 2014 03:44:21 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by mail.everdot.org (Postfix) with ESMTP id C12D09122CA7
 for <tor-talk@lists.torproject.org>; Fri,  1 Aug 2014 03:44:20 +0200 (CEST)
X-Virus-Scanned: amavisd-new at everdot.org
Received: from mail.everdot.org ([127.0.0.1])
 by localhost (everdot.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id RANriRq7KWJ6 for <tor-talk@lists.torproject.org>;
 Fri,  1 Aug 2014 03:44:14 +0200 (CEST)
Received: from meilong (unknown [IPv6:2001:470:dc2e:2:4807:3c6b:468:80fe])
 (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.everdot.org (Postfix) with ESMTPSA id B51CC9122B91
 for <tor-talk@lists.torproject.org>; Fri,  1 Aug 2014 03:44:14 +0200 (CEST)
Date: Fri, 1 Aug 2014 03:44:08 +0200
From: =?ISO-8859-1?B?1nl2aW5k?= Saether <oyvinds@everdot.org>
To: tor-talk@lists.torproject.org
Message-ID: <20140801034408.4895a1d5@meilong>
In-Reply-To: <1877401614.7764.1406640591875.JavaMail.zimbra@apawc.com.au>
References: <1877401614.7764.1406640591875.JavaMail.zimbra@apawc.com.au>
X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.24; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Subject: Re: [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: multipart/mixed; boundary="===============7726674998024538305=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

--===============7726674998024538305==
Content-Type: multipart/signed; micalg=PGP-SHA1;
 boundary="Sig_/tkjYdH/PsirUvNyWMDccfFE"; protocol="application/pgp-signature"

--Sig_/tkjYdH/PsirUvNyWMDccfFE
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

> 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.

So I run the relay with a VE and now I get to see what everyone using
that VE is doing? I am not sure this is a good idea.

--Sig_/tkjYdH/PsirUvNyWMDccfFE
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlPa8OsACgkQNBSJHnwv/KrNRgCfXaI2awrviALfRk1ttgUI7c2+
424Anj9Yo4gO8c+t0V6oe8y4rEJgMRW6
=iC7/
-----END PGP SIGNATURE-----

--Sig_/tkjYdH/PsirUvNyWMDccfFE--

--===============7726674998024538305==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============7726674998024538305==--

