Delivery-Date: Sun, 12 Oct 2014 21:47:45 -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 B82311E0F5C;
	Sun, 12 Oct 2014 21:47:43 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9A3313139C;
	Mon, 13 Oct 2014 01:47:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 55F023139C
 for <tor-talk@lists.torproject.org>; Mon, 13 Oct 2014 01:47:36 +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 oHwMSmGAEFnF for <tor-talk@lists.torproject.org>;
 Mon, 13 Oct 2014 01:47:36 +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 2A58031393
 for <tor-talk@lists.torproject.org>; Mon, 13 Oct 2014 01:47:36 +0000 (UTC)
Received: from [82.94.249.234] (latitanza [82.94.249.234]) (Authenticated
 sender: griffin@cryptolab.net) by localhost (Postfix) with ESMTPSA id
 83AA5120B61; Mon, 13 Oct 2014 01:47:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptolab.net;
 s=stigmate; t=1413164852;
 bh=RbIRvq6m3yy618tMAVmfhmKVrfARrGMCgMb140IFlpg=;
 h=Date:From:To:Cc:Subject:In-Reply-To:References;
 b=lS8B/+WooHATnWqjL0O3j7c1+DenrH3/QeZCCGbzhXiPY9vutH1O5zUxrRYK3zbri
 omAkeKlaxbSgWgfk9H3Kh23DxuYWAFLrj4MAO9fnaMkUBuVAgx66VLV8ljQYaXM5L1
 ZCegcEbv723f63vmjStUnQGpGamed32FBOyGhcZY=
MIME-Version: 1.0
Date: Sun, 12 Oct 2014 21:47:32 -0400
From: Griffin Boyce <griffin@cryptolab.net>
To: tor-talk@lists.torproject.org
In-Reply-To: <44BDACD3189.00000851beatthebastards@inbox.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>
Message-ID: <c89dfc787bb0b5459316f6baaf85022a@cryptolab.net>
X-Sender: griffin@cryptolab.net
User-Agent: Roundcube Webmail
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>

I wrote:
> Isis,
> 
> Why, then, has there been discussion of the use of Raspberry Pis
> without mention of this?

   People have taken it upon themselves to run relays on raspis, but 
that's not exactly Tor's fault.

   It seems really obvious not to run a relay off of an extremely 
low-power computer.  IRL, I always try to convince people not to do it, 
but it rarely works.  Honestly I would recommend against it even for a 
bridge, but there's something to be said for having increased address 
diversity at the expense of performance.  (But I *also* don't want 
bridge users to be penalized for needing to use a bridge).

   Raspberry Pis are decent for most running hidden services, however 
they suck royally for relays.

   But to answer your actual question: because we each only have a finite 
amount of time and can't respond to every thread.  As for what to run a 
relay on, there are very small servers that run about $100 that get the 
job done.

   I follow the "1 rule" -- At a bare minimum, 1GB RAM & 1Ghz CPU, 
connected via ethernet, with "RelayBandwidthRate 1000 KB" set in torrc. 
This is for a dedicated machine that only runs a relay. Not a raspi, not 
your phone, not a cafe wifi in Kamchatka. Test your internet speed 
before setting up your relay and you may be pleasantly surprised at how 
much throughput you can get. =) Helping the network is really important, 
but you want to make sure that you're not actually hurting the network 
on accident.

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

