Delivery-Date: Fri, 25 Jul 2014 20:42:13 -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 86B1B1E0A74
	for <archiver@seul.org>; Fri, 25 Jul 2014 20:42:11 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 301A9303BB;
	Sat, 26 Jul 2014 00:42:09 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 7896D303E7
 for <tor-talk@lists.torproject.org>; Sat, 26 Jul 2014 00:38: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 Nc5OdJUzms_D for <tor-talk@lists.torproject.org>;
 Sat, 26 Jul 2014 00:38:55 +0000 (UTC)
Received: from patternsinthevoid.net (greyarea.patternsinthevoid.net
 [106.187.37.158])
 by eugeni.torproject.org (Postfix) with ESMTP id 124B3303C5
 for <tor-talk@lists.torproject.org>; Sat, 26 Jul 2014 00:38:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by patternsinthevoid.net (Postfix) with ESMTP id E5E8A3A1414
 for <tor-talk@lists.torproject.org>; Sat, 26 Jul 2014 00:38:49 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at patternsinthevoid.net
Received: from patternsinthevoid.net ([127.0.0.1])
 by localhost (greyarea.patternsinthevoid.net [127.0.0.1]) (amavisd-new,
 port 10024)
 with ESMTP id aqs_m8GJ9hfa for <tor-talk@lists.torproject.org>;
 Sat, 26 Jul 2014 00:38:44 +0000 (UTC)
Date: Sat, 26 Jul 2014 00:38:27 +0000
From: isis <isis@torproject.org>
To: tor-talk@lists.torproject.org
Message-ID: <20140726003827.GT7899@patternsinthevoid.net>
References: <53D16B7A.6000100@cpunk.us> <20140724203626.GS7408@moria.seul.org>
 <53D177B8.4010306@riseup.net>
 <20140725231953.GR7899@patternsinthevoid.net>
MIME-Version: 1.0
In-Reply-To: <20140725231953.GR7899@patternsinthevoid.net>
X-GPG-Public-Key-URL: https://blog.patternsinthevoid.net/isis.txt
X-Louis-Lingg: In this hope do I say to you I despise you. I despise your
 order, your laws, your force-propped authority. Hang me for it!
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: multipart/mixed; boundary="===============9210535667525238819=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


--===============9210535667525238819==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="Bk6L21jbBNK7V1Rv"
Content-Disposition: inline


--Bk6L21jbBNK7V1Rv
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

isis transcribed 4.9K bytes:
> Mirimir transcribed 1.5K bytes:
> > On 07/24/2014 02:36 PM, Roger Dingledine wrote:
> > > On Thu, Jul 24, 2014 at 03:24:26PM -0500, Cypher wrote:
> > >> In light of the last year of disclosures by Edward Snowden, why is T=
or
> > >> requiring that I establish an account with an email provider that is
> > >> completely out of my control and has a general history of complying =
with
> > >> law enforcement data requests? Why those two providers specically?
> > >=20
> > > 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.
> > >=20
> > > https://svn.torproject.org/svn/projects/design-paper/blocking.html#tt=
h_sEc7.4
> >=20
> > That totally makes sense.
> >=20
> > > (Also, it recently became clear that it would be useful for people to
> > > access this provider via https, rather than http, so a network advers=
ary
> > > can't just sniff the bridge addresses off the Internet when the user
> > > reads her mail. And it would also be nice to not use providers that t=
urn
> > > their entire email databases over to the adversary, even unwittingly.
> > > Lots of adversaries and lots of goals to manage at once here.)
> > >=20
> > > --Roger
> >=20
> > Right, and with HTTPS, users' ISPs (and their friends) can't even see
> > that bridges are being provided. Does the bridge database talk directly
> > with Google and Yahoo mail servers, to prevent possible XKeyScore snoop=
ing?
>=20
> In addition to requiring that an email provider enforce some base difficu=
lty
> level for obtaining new accounts, BridgeDB requires that a provider must =
have:
>=20
>  1) TLS enabled for both their SMTP and webmail/IMAP/POP interfaces. Usin=
g TLS
>     when sending and receiving to/from the provider from BridgeDB is
>     required. [0]
>  2) Verifiable DKIM signatures on the user's outgoing emails.=20
>=20
> I've long been in favour of removing Yahoo from the accepted providers. [=
1]
> However, we've decided not to do that for the sake of people who have alr=
eady
> followed BridgeDB's instructions and obtained Yahoo email addresses, and =
we've
> opted for a different solution instead. [2]
>=20
> I'm also strongly in favour of adding Riseup! to the list of acceptable
> providers, as I believe that their account security, commitment to their
> users, unwillingness to hand over logs, and difficulty of account creatio=
n to
> be orders of magnitude better than any other email provider out there. I'm
> currently working with the Riseup! birds to get (2) enabled so that we ca=
n do
> this. [3]
>=20
> [0]: https://trac.torproject.org/projects/tor/ticket/10989
> [1]: https://trac.torproject.org/projects/tor/ticket/11140
> [2]: https://trac.torproject.org/projects/tor/ticket/11330
> [3]: https://trac.torproject.org/projects/tor/ticket/11139


And... obviously, five minutes after I sent that email, I realised that
Riseup!'s DKIM signature now checks out fine, meaning that you all should n=
ow
be able to email BridgeDB from a riseup.net email address to receive
bridges. [0]

Thank the Riseup! birds for fixing this (and for being all around a great
bunch of people with everything they do). <3

[0]: https://trac.torproject.org/projects/tor/ticket/11139#comment:15

--=20
 =E2=99=A5=E2=92=B6 isis agora lovecruft
_________________________________________________________
GPG: 4096R/A3ADB67A2CDB8B35
Current Keys: https://blog.patternsinthevoid.net/isis.txt

--Bk6L21jbBNK7V1Rv
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQMhBAEBCgELBQJT0viDBYMB4TOAVhSAAAAAACUAKGlzaXMrc2lnbnN1YmtleUBw
YXR0ZXJuc2ludGhldm9pZC5uZXRGQzYzQUE1Q0QxOTM4NjlDMzIzNzE0NUE1QzE3
Nzc2RTI3RjdFODRESxSAAAAAABoAKGlzaXNAcGF0dGVybnNpbnRoZXZvaWQubmV0
MEE2QTU4QTE0QjU5NDZBQkRFMThFMjA3QTNBREI2N0EyQ0RCOEIzNS4aaHR0cHM6
Ly9ibG9nLnBhdHRlcm5zaW50aGV2b2lkLm5ldC9wb2xpY3kudHh0LJhodHRwczov
L2Jsb2cucGF0dGVybnNpbnRoZXZvaWQubmV0L2lzaXMudHh0AAoJEFwXd24n9+hN
R/kP/A7HCxJGkAPO5D1NxvkpfNzeT28E1L3uDPVzlb88jkghbrWmRBHa/K1rQ4Fq
vsbp7vp2PKlIQou5oXu3eNM1p1lo7eFxikC+xX9qrHi9Aohh71DbYFgCFIqe4MuG
atZhWR241kMuLe9DU8OfrnRZFDxc32gRxRr7vLQaII8T3QZgNwnWknBtYr0wcqsp
v9J54tmFFRLqO8By3vSfWKNWT9eHg898Mqd8mU5GuEji5AVsUknkwqTgALppHcI+
f/tZtdGc4NTuhAf2204iXpbOynK3cMPWFm1r5mnThRae/BUgMREZVl687Mh+tOQl
xs3yiiTSfl1Qu1gKFUiR2AmPu1dgR+eXrJXqIMaBLAj/sOuAhoyFttHvSpBy1E9B
/tI7pCy+7zSnO3v8NNfMQSb2XvxPrxkUftK0+2x7GOcfBILGXsQwhhrAMlTss1FQ
V8TdzZZ5LVRCjEzxo+1Yty7WuOqWhdn3Em83n3qtxvLPXYWr0HVYyzAoMLXASMq7
D2NdNv9pDquRopKhOoS3z2q0EDWc9Cu7m3L4cPrqDcAbUjnwiBTGCtFLgM+E38QR
5b6fY1EQNXOoLuoqAGx28ufp4gGvWALFjk6m0YFZHl7NCUQLJ1Qw0qpCXL4YDrRy
M0OKexqlaD8hHvITq38Rpw6QRFsLozTz/OnplD8S75LWt5Kt
=uCnr
-----END PGP SIGNATURE-----

--Bk6L21jbBNK7V1Rv--

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

--===============9210535667525238819==--

