Delivery-Date: Mon, 08 Sep 2014 20:06:07 -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 86AE01E02C5;
	Mon,  8 Sep 2014 20:06:05 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B0DE52D328;
	Tue,  9 Sep 2014 00:06:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3E9F42D2F7
 for <tor-talk@lists.torproject.org>; Tue,  9 Sep 2014 00:05:57 +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 edigIubS4WTA for <tor-talk@lists.torproject.org>;
 Tue,  9 Sep 2014 00:05:57 +0000 (UTC)
Received: from khazad-dum.seul.org (khazad-dum.csail.mit.edu [128.31.0.47])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "moria.seul.org", Issuer "moria.seul.org" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 225222CDA5
 for <tor-talk@lists.torproject.org>; Tue,  9 Sep 2014 00:05:57 +0000 (UTC)
Received: by khazad-dum.seul.org (Postfix, from userid 501)
 id 19A421E0B30; Mon,  8 Sep 2014 20:05:54 -0400 (EDT)
Date: Mon, 8 Sep 2014 20:05:54 -0400
From: Roger Dingledine <arma@mit.edu>
To: tor-talk@lists.torproject.org
Message-ID: <20140909000553.GN8132@moria.seul.org>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-12-10)
Subject: [tor-talk] What should our 31c3 talk be?
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>

The 31c3 talk proposals are due this coming Sunday:
http://events.ccc.de/2014/07/12/31c3-call-for-participation-en/

I wonder what would be the most useful topic for this year?

In brainstorming with folks on IRC, here are four options:

--------

1) An update on pluggable transports: obfs3, obfs4, FTE, librtc and
uproxy, and other acronyms you don't recognize. Many transports are now
integrated into the default Tor Browser, we're starting to get some more
useful usage statistics, and pluggable transports have played an important
role in various countries in recent years. Plus we're soon going to start
some projects on evaluation and comparison of transport designs, e.g.
https://trac.torproject.org/projects/tor/wiki/org/sponsors/SponsorS/PluggableTransports/Proposal

One of the most intriguing pieces of pluggable transports lately is
the convergence of "make it hard to DPI for the protocol so the censor
can't block it" with "make it hard to DPI for the protocol so the global
surveillance adversary doesn't know to add that flow to its database".
In particular, systems like Flashproxy might be especially effective
against the global surveillance adversary, since the many transient
addresses that separate the users from the known Tor relay addresses
make it harder to build a list of users that are worth watching.

2) News on the Tor Browser front: all about our deterministic builds, and
what they get us, and who else is jumping on the bandwagon. A discussion
of the upcoming secure update mechanism, and what security properties
it does/doesn't get us. Tradeoffs with blocking or not blocking ads,
or with enabling or disabling javascript.

3) Double down on the transparency push: walk through all the entries
in https://trac.torproject.org/projects/tor/wiki/org/sponsors and
explain what we're doing for each of them. I think it would be useful
for more of the Tor community to know more details here, but I'm not
sure how to do it in a way that doesn't just turn into a big laundry
list, like the 29c3 talk did:
http://events.ccc.de/congress/2012/Fahrplan/events/5306.en.html

4) Some sort of more generic Q&A where we raise a bunch of topics
to start, and then inefficiently take questions from the audience,
try to make sense of them, and then talk about whatever comes to mind
in response.

--------

Two lessons I've learned from recent CCC talks:

A) Social commentary works much better than technical things. That is,
the audience respects us for our technical work, and now they want to hear
our perspective on what's going on in the world. So while my instinct
is to use the talks to make the audience more technically competent and
thus more able to help us in this growing global conflict, the talks
that work best these days are more like social rallies.

B) It won't work to pick a more technical topic and ask for a smaller room
to focus on the people who most want to help. The room will still get
mobbed by thousands of people who are there 'for the show'. We learned
this lesson in 29c3. And to be fair, Tor is a major component in the
modern security and privacy conversation, so following what Tor has to
say, even if you're not planning to do anything to help, makes sense.

Is there a fifth topic I should be considering?

So far item 1, the pluggable transport one, seems most plausible to me.

--Roger

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

