Delivery-Date: Sun, 10 Jan 2016 10:29:36 -0500
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 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 14A211E003A;
	Sun, 10 Jan 2016 10:29:35 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8EA3837F9C;
	Sun, 10 Jan 2016 15:29:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B794D374E9
 for <tor-talk@lists.torproject.org>; Sun, 10 Jan 2016 15:29:25 +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 HK9sy14BpOUC for <tor-talk@lists.torproject.org>;
 Sun, 10 Jan 2016 15:29:25 +0000 (UTC)
Received: from mail.headstrong.de (mail.headstrong.de [81.7.4.112])
 (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 8925135ADA
 for <tor-talk@lists.torproject.org>; Sun, 10 Jan 2016 15:29:25 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1])
 by mail.headstrong.de (Postfix) with ESMTP id 7E17A1C003CB
 for <tor-talk@lists.torproject.org>; Sun, 10 Jan 2016 16:29:21 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=headstrong.de;
 h=content-transfer-encoding:content-type:content-type
 :in-reply-to:mime-version:date:date:message-id:from:from
 :references:subject:subject:received; s=mail; t=1452439761; x=
 1454254162; bh=LcZyY8Mwb4iiEmuUtxE+KA74ogtutYLSMtIvuvr+Ehg=; b=B
 KgqEo7SzQFoBNVtcIaAuk+wfrwHCTgIkA9/+vHaPnidnRxvmbxy3S91JsfT22I8a
 e6kULOVMXIRqR6SgkydbRfKw3Z3kJpaE+EdVcmiNCqeOYiVEUHocjfVLUMGzbgTM
 yGjQdXX4IBNO7G+rxVuzlWy9YymuhC00Ns6bSZ3Vkw=
X-Virus-Scanned: Debian amavisd-new at mail.headstrong.de
Received: from mail.headstrong.de ([127.0.0.1])
 by localhost (mail.headstrong.de [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id XXicOvg2QqZt for <tor-talk@lists.torproject.org>;
 Sun, 10 Jan 2016 16:29:21 +0100 (CET)
To: tor-talk@lists.torproject.org
References: <569265F3.6040109@infosecurity.ch>
From: Moritz Bartl <moritz@torservers.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <569278D0.8080301@torservers.net>
Date: Sun, 10 Jan 2016 16:29:20 +0100
MIME-Version: 1.0
In-Reply-To: <569265F3.6040109@infosecurity.ch>
Subject: Re: [tor-talk] Funding Tor Development trough Referral/Affiliate
 Marketing
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>

On 01/10/2016 03:08 PM, Fabio Pietrosanti (naif) - lists wrote:
> I'm wondering if that couldn't be a very interesting model also for
> TorBrowser, whereby the TorBrowser would automatically inject a referral
> ID (in the HTTP header or URL parameters) [...]
> That kind of model could be implemented with a custom plug-in within the
> Tor Browser.

My first reaction was that this is highly unethical.

I can see this happening as a plugin and an option within the setup
wizard to enable it (opt-in). It can probably be done similarly to the
proof-of-concept HTTPS Everywhere ruleset
https://github.com/chris-barry/darkweb-everywhere

I still don't have a very good feeling about it.

-- 
Moritz Bartl
https://www.torservers.net/
-- 
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

