Delivery-Date: Sat, 26 Jul 2014 17:56:52 -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_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	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 04EC31E0A44
	for <archiver@seul.org>; Sat, 26 Jul 2014 17:56:51 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3D3362E740;
	Sat, 26 Jul 2014 21:56:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 261102973C
 for <tor-talk@lists.torproject.org>; Sat, 26 Jul 2014 21:55:27 +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 IwYHSE56jBXD for <tor-talk@lists.torproject.org>;
 Sat, 26 Jul 2014 21:55:27 +0000 (UTC)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com
 [IPv6:2607:f8b0:4001:c03::229])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id F12AB2DD67
 for <tor-talk@lists.torproject.org>; Sat, 26 Jul 2014 21:55:26 +0000 (UTC)
Received: by mail-ie0-f169.google.com with SMTP id rd18so5127175iec.0
 for <tor-talk@lists.torproject.org>; Sat, 26 Jul 2014 14:55:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=+khp/7YHXkf7IFBGQgYdGH/wBb+OMgrnNlT+GYbyNMk=;
 b=jz2pVbCGIo/VMPBO6LupRWkHz1c8vA9ORNOMTjUYppvirqHLHLStZAC9YN/e6c7orR
 QO2hJRgIKJZzuBy/z4qRgQblOOb7eOKKy9bxfpx/aSe4E1Wh+Kj6D0IAOIG0A93EUNws
 gG7WTQBy0VHhNKzo9AGg6TxPQeFZJslcolfqnwGA4eQReAsewDpY5K5aA+7g8I1vpm4X
 DcIpx7BjTOHyLazEhY3embS4egcnbEw22g40bkwYmTMNFF46nnwaIryb75p92iKN30k0
 Uqv31a+prPqdUlBjMHShxvmI/rDubqbV9xA4SCcrYZeX7S73lUKWnXAeDQtuHDMC9miD
 0P7A==
MIME-Version: 1.0
X-Received: by 10.50.112.1 with SMTP id im1mr17356509igb.33.1406411724712;
 Sat, 26 Jul 2014 14:55:24 -0700 (PDT)
Received: by 10.64.30.194 with HTTP; Sat, 26 Jul 2014 14:55:24 -0700 (PDT)
In-Reply-To: <20140726074722.GA16694@localhost>
References: <53D16B7A.6000100@cpunk.us> <20140724203626.GS7408@moria.seul.org>
 <20140725154421.GB14229@badger> <20140726074722.GA16694@localhost>
Date: Sat, 26 Jul 2014 21:55:24 +0000
Message-ID: <CAP-DOiTppnp7MD6jPFA+Mk5-xpL-7pU4sr014L3kaoPcoDcefQ@mail.gmail.com>
From: ideas buenas <ideasbuenas@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
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>

I don't trust Google neither Yahoo nor Bing. If they have captchas and your
phone then they're done and you're screwed. Don't be afraid of using Riseup
a lot. They are in the market. But I think, Roger can do something with
this (sorry, I talk to the boos, not to the hand). Perhaps he don't because
there are more people talking of Tor than using it. Cheers.


On Sat, Jul 26, 2014 at 7:47 AM, Matthew Finkel <matthew.finkel@gmail.com>
wrote:

> On Fri, Jul 25, 2014 at 03:44:21PM +0000, obx wrote:
> > > Because we need an adequately popular provider that makes it hard to
> > > generate lots of addresses. Otherwise an attacker could make millions
> > > of addresses and "be" millions of different people asking for bridges.
> >
> > I know this is the reason, but there are still captchas, right?
> >
>
> Yes, they do rely on captchas and phone numbers. But luckily, in the
> case for gmail, the capture-difficulty is variable. This in no way
> solves the problem, but it's certainly better than most alternatives.
>
> > Also, I think this list needs to be expanded.
> >
> > > (Also, it recently became clear that it would be useful for people to
> > > access this provider via https, rather than http, so a network
> adversary
> > > can't just sniff the bridge addresses off the Internet when the user
> > > reads her mail.
> >
> > I'm not sure if gmail is safe against this recent adversary, regardless
> > of the protocol.
> >
>
> Excluding the NSA/US Gov, I think gmail is the best
> corporate-controlled service available, right now. This
> opinion may change if contradictory information is released, but at
> this time, for our purposes, I am happy requiring gmail.
>
> Services like riseup are excellent, but we are abusing their systems
> (a little), as well as potentially putting more work/stress/pressure on
> the staff. I wish there was a way to necessitate the requirements and
> rigor of riseup with the scalability of gmail. Alas, this isn't
> available, as far as I know. Riseup is also special due to existing
> person relationships, it's possible we can expand the whitelist to other
> provides such as autistici, but it will be a more involved process.
>
> Suggestions and help always appreciated
> --
> 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
>
-- 
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

