Delivery-Date: Thu, 24 Jul 2014 18:57:35 -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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY
	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 F01571E0240
	for <archiver@seul.org>; Thu, 24 Jul 2014 18:57:33 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B5D6E2F19E;
	Thu, 24 Jul 2014 22:57:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 6A51C2E961
 for <tor-talk@lists.torproject.org>; Thu, 24 Jul 2014 22:45:28 +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 Bwb48TNIffFL for <tor-talk@lists.torproject.org>;
 Thu, 24 Jul 2014 22:45:28 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 464452DCE5
 for <tor-talk@lists.torproject.org>; Thu, 24 Jul 2014 22:45:28 +0000 (UTC)
Received: from fulvetta.riseup.net (fulvetta-pn.riseup.net [10.0.1.75])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified))
 by mx1.riseup.net (Postfix) with ESMTPS id 68D97553BE
 for <tor-talk@lists.torproject.org>; Thu, 24 Jul 2014 15:45:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riseup.net; s=squak;
 t=1406241925; bh=VSAiKL6n2/alG3UCrV7qWO8ZFW0wpes3C1kiswje61c=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=VGb6GQhSA+s7jfQJMP0h19AKMbGjmB2CEA9O3WCFC3+RoWjMamb571dVhPtiRHj/Z
 XtprbBmvF5BeZtfjRlS/ByarDAQQZexY/DXyzjgBEUzBbN3Y71Yk80xQryyFfKr5g4
 EmNYZTcTdU7Uj66RROE0e+rxbMpnLXykSojXNzWY=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir@fulvetta.riseup.net)
 with ESMTPSA id 6D1F1204
Message-ID: <53D18C80.8020503@riseup.net>
Date: Thu, 24 Jul 2014 16:45:20 -0600
From: Mirimir <mirimir@riseup.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <53D16B7A.6000100@cpunk.us> <20140724203626.GS7408@moria.seul.org>
 <53D177B8.4010306@riseup.net> <53D17AD6.4050803@sec.gd>
 <53D180B2.4060800@riseup.net> <53D181B5.1030205@sec.gd>
In-Reply-To: <53D181B5.1030205@sec.gd>
X-Enigmail-Version: 1.6
X-Virus-Scanned: clamav-milter 0.98.1 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] Why does requesting for bridges by email require a
 Yahoo or Gmail address?
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 07/24/2014 03:59 PM, mal wrote:
> On 07/24/2014 05:54 PM, Mirimir wrote:
>> I suspect that Google and Yahoo require cellphone text confirmation for
>> multiple account attempts from a single IP address. There are
>> workarounds, but there's more required than cheap labor.
> 
> Correct, but if a million people in your developing country of choice
> phones and/or pre-existing gmail or yahoo accounts take you up on your
> five cent offer...
> 
> Gmail, at least, allows for 4 or 5 accounts per phone number. If yahoo
> does the same, that's 8 to 10 per person.

Yes, it's doable, but at least it's harder than scraping a website.

One could have the start-tor-browser script generate a unique key at
first run, based on the hashed time (nanosecond accuracy) that the
download had completed. Users would need to include the key with the
bridge request. The bridge database could ignore multiple requests from
a given key, or limit them appropriately. The keys could be passed on to
the bridges, and each bridge would accept connections only from its
assigned clients.

The process could be totally hidden for normal users. But each account
would require a separate download and installation.
-- 
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

