Delivery-Date: Mon, 13 Oct 2014 01:00:25 -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=-3.9 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_SIGNED,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 392281E0CB1;
	Mon, 13 Oct 2014 01:00:24 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DE08E31427;
	Mon, 13 Oct 2014 05:00:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A69603140C
 for <tor-talk@lists.torproject.org>; Mon, 13 Oct 2014 05:00:17 +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 Ai8WNb9nIf0x for <tor-talk@lists.torproject.org>;
 Mon, 13 Oct 2014 05:00:17 +0000 (UTC)
Received: from latitanza.investici.org (latitanza.investici.org
 [IPv6:2001:888:2000:56::19])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.autistici.org",
 Issuer "Autistici/Inventati Certification Authority" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 5ECD5313AB
 for <tor-talk@lists.torproject.org>; Mon, 13 Oct 2014 05:00:17 +0000 (UTC)
Received: from [82.94.249.234] (latitanza [82.94.249.234]) (Authenticated
 sender: griffin@cryptolab.net) by localhost (Postfix) with ESMTPSA id
 6BCFB120B47; Mon, 13 Oct 2014 05:00:14 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptolab.net;
 s=stigmate; t=1413176414;
 bh=rR+lm45ZpbqJ6gkoShR2+mAnVhgbfEk2c2A00fvaEK4=;
 h=Date:From:To:Cc:Subject:In-Reply-To:References;
 b=fyVTcv+b4/n+aRZ+sHUxVDB1ggHeU0EGUFiBoRG4SUBT+IN7Gl+7/jIDw3X1E1U/A
 vxKgpJh1i+LZS8VfncwOBYgHu9mKQtMME6C09MQJB1e91QBjTGrJjuGir9gdftTZBq
 G1Qur9xtXHaXO55PCXxGi1x9l3mdTx6FctE9Pt2Q=
MIME-Version: 1.0
Date: Mon, 13 Oct 2014 01:00:14 -0400
From: Griffin Boyce <griffin@cryptolab.net>
To: Casey Rodarmor <casey@rodarmor.com>
In-Reply-To: <CANLPe+Nd+FonS8+x+DEKZB6BZmCVWBqYk01pG-_TCVu=o34j+A@mail.gmail.com>
References: <597899488.3907271413062124086.javamail.root@ip-10-181-20-37.ec2.internal>
 <719492467.3957621413068678816.javamail.root@ip-10-181-20-37.ec2.internal>
 <canlpe+m-mqkbxc3jah5oggra7j-7ju-kj0tzj0z1ms8r0apgng@mail.gmail.com>
 <20141011231732.ge54413@moria.seul.org>
 <canlpe+nlookeocoyk6npy2tdzs+gmpyzqdntiyyqfphitwpvng@mail.gmail.com>
 <44BDACD3189.00000851beatthebastards@inbox.com>
 <c89dfc787bb0b5459316f6baaf85022a@cryptolab.net>
 <9e34afb55dc79c67e72a35f9faa431d0@cryptolab.net>
 <CANLPe+M7utUa9Q=MzoC1E_tYkGg9WCK_ERGbAup20X8VbLkcpw@mail.gmail.com>
 <1c79d806d7a7d71f7ca3b00a10042591@cryptolab.net>
 <CANLPe+Nd+FonS8+x+DEKZB6BZmCVWBqYk01pG-_TCVu=o34j+A@mail.gmail.com>
Message-ID: <06d961216e5fce4bb01ff234b9d12ed7@cryptolab.net>
X-Sender: griffin@cryptolab.net
User-Agent: Roundcube Webmail
Cc: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Tor Relay Smartphone App
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Casey Rodarmor wrote:
>> There are lots of issues with hardware projects and it costs an
>> obscene amount of money -- not to mention the implications on
>> security and anonymity that it would introduce.
> 
> Do you think there's any way it could be done without creating said
> problems for security and anonymity?

   No.  There's an open debate about the overall security of *any* 
manufacturing process, but the issue remains that the mail system in any 
country is inherently insecure.  Secure hardware delivery does not 
exist.

   As for anonymity, exchanging money removes anonymity.  There is no 
truly anonymous currency.

> "Tor Awesomeness Compliant" and a cute cartoon onion

   Cute. =) But I don't really see the benefit of this.  It seems like a 
lot of extra work for no real benefit.  If the issue is that people 
don't always have a clear idea of what hardware will work for relays 
(hardware they likely already have!) then this doesn't even approach it. 
  If the secondary issue is that people are bummed out that 
raspis/beaglebones shouldn't run relays, that is *also* not fixed by Tor 
undertaking a massive hardware project.

>> This could work, but would need a maintainer.
> 
> So, just totally totally hypothetically, not trying to sign up for yet
> another project that I don't know if I have time for

   I say that interested people should come up with ideas for how to pull 
it off, code it up, put it on github with a large "Danger! High 
Voltage!" warning, and get feedback from the rest of the community. =) 
That's how people get started and learn.

> That's a good idea, but I think that hardware compatibility is a big
> issue here, especially for non-technical users who might not be able
> to find and install linux drivers for whatever strange hardware that
> they have. A custom image that can control all dependencies and have
> full permissions to fetch and install whatever drivers it needs

   A custom image wouldn't necessarily be able to solve driver 
compatibility issues better than stock Debian/Ubuntu (though Ubuntu is 
better for quirky hardware than Debian).  If you install Debian and 
don't have the right ethernet or display drivers, you're still going to 
use a different machine to connect to the internet and look up the 
solution.  Because you don't have access to the internet on the 
missing-ethernet-driver machine.  This is kind of a bootstrapping 
problem.

   This is one of the few projects where I'd say hardware compatibility 
isn't a factor.  If you can run Debian, you can run Tor (even if you 
can't be effective as a relay).

best,
Griffin

-- 
"I believe that usability is a security concern; systems that do
not pay close attention to the human interaction factors involved
risk failing to provide security by failing to attract users."
~Len Sassaman
-- 
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

