Delivery-Date: Sun, 12 Oct 2014 18:38:44 -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 E24601E0E1D;
	Sun, 12 Oct 2014 18:38:41 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 917D2311F5;
	Sun, 12 Oct 2014 22:38:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 49C10311C6
 for <tor-talk@lists.torproject.org>; Sun, 12 Oct 2014 22:38:34 +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 kUWURUAJtuaS for <tor-talk@lists.torproject.org>;
 Sun, 12 Oct 2014 22:38:34 +0000 (UTC)
Received: from mail-vc0-f174.google.com (mail-vc0-f174.google.com
 [209.85.220.174])
 (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 2175331136
 for <tor-talk@lists.torproject.org>; Sun, 12 Oct 2014 22:38:34 +0000 (UTC)
Received: by mail-vc0-f174.google.com with SMTP id hq12so5034070vcb.19
 for <tor-talk@lists.torproject.org>; Sun, 12 Oct 2014 15:38:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to:content-type;
 bh=nxkHjxXrNdr5Z06Cdu4nvkVshgHQVC5Dj6ljyNyQYLc=;
 b=eov0N3luIvmaOXa+TgXtaj38wG/J9zrflF7sWyTZ4HxxGCvPrzpxBZiPQof5/CFOOs
 Y47NvY0h1anWAaUhHiEq7PZJwDn99tmmzHvSMZqucp4zoOs5GwqDvjQSxd961ejK6XG/
 amzg+RgN4gxlQGsSp3ObT4QXRIoVK5HDToLJBb+5dFwWBRWtvppU7XQKsXX2SWofwVZa
 68l6tiY8Rfh/+cEag2xsQxufrWdrAKIuvj4Ftx2MJPbLyoti1HqqLjbK9/bho2uLZj8Q
 piFNk3SivSD4AYh0BO6uERQJE/qhXmllsEfRk90GZ/P0BrLdP7HQtgJf3RP4zFlDDpfb
 pApQ==
X-Gm-Message-State: ALoCoQkByDZI7+v4lVfwa89WGRn54o9uaA0dueYkszpBPrCzPjkJDZW9mWvC+Z6Ovut4A+LU/MGo
MIME-Version: 1.0
X-Received: by 10.221.41.2 with SMTP id ts2mr16993625vcb.23.1413153511698;
 Sun, 12 Oct 2014 15:38:31 -0700 (PDT)
Received: by 10.220.40.2 with HTTP; Sun, 12 Oct 2014 15:38:31 -0700 (PDT)
In-Reply-To: <CANLPe+OKKx1rbDUaWfvHTXcAswuDKs55rYb67k3evBMMX+e3BQ@mail.gmail.com>
References: <CANLPe+M-MqKbxC3Jah5OggRa7j-7jU-KJ0tZJ0Z1mS8r0aPgNg@mail.gmail.com>
 <597899488.3907271413062124086.JavaMail.root@ip-10-181-20-37.ec2.internal>
 <719492467.3957621413068678816.JavaMail.root@ip-10-181-20-37.ec2.internal>
 <20141011231732.GE54413@moria.seul.org>
 <CANLPe+NLOokeocoYk6nPY2Tdzs+GMPYZQDNtiyyqFPhiTWpvng@mail.gmail.com>
 <20141012213222.GJ10167@patternsinthevoid.net>
 <CANLPe+OKKx1rbDUaWfvHTXcAswuDKs55rYb67k3evBMMX+e3BQ@mail.gmail.com>
Date: Mon, 13 Oct 2014 07:38:31 +0900
Message-ID: <CANLPe+MACaixayYRDU-TCyTyV_De7dcnoQN4GTf-0AmFFj+jYQ@mail.gmail.com>
From: Casey Rodarmor <casey@rodarmor.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
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-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>

Also, a sort of related question: Would a dedicated raspberry pi with a
decent OS on a high-quality 100M/100M connection do more harm than good?
Would it be able to push significant traffic with its CPU?

On Mon, Oct 13, 2014 at 7:28 AM, Casey Rodarmor <casey@rodarmor.com> wrote:

> Thank you very much for the pointer to that thread, super interesting!
>
> On Mon, Oct 13, 2014 at 6:32 AM, isis <isis@torproject.org> wrote:
>
>> The problem is this: All clients fetch information about all the relays
>> in the
>> network from the Directory Authorities/Mirrors, and these fetches take up
>> a
>> certain amount of bandwidth. If the relay is too slow, the bandwidth
>> provided
>> by that relay does not compensate for the directory fetching bandwidth
>> used to
>> tell people about the relay, and thus it is actively harming the network.
>>
>
> This is probably a silly question, but why don't nodes themselves gossip
> in a P2P fashion about other nodes they've seen or heard about, in order to
> avoid taxing directory authorities and mirrors? I'm sure that there are
> security implications for this, but perhaps they could be overcome by
> preferring nodes in different IP blocks and with diverse traceroutes, etc.
>
>
>> Additionally, since Tor processes are normally CPU-bound, most relays
>> aren't
>> able to use all their available bandwidth with a single Tor process.
>> Running a
>> relay on ARM (or likely any other mobile/low power) CPU will only further
>> limit how much traffic your relay is actually pushing.
>>
>
> Is this because of the outer encryption wrapper layer decryption?
>
>
>> Additionally, if you're attempting to do this with Orbot on an Android
>> device,
>> you'll run into issues with Android's process management system and the
>> Tor
>> process randomly dying unexpectedly. This means that you are providing an
>> unreliable, flapping relay which is actively messing up other people's
>> connections through the Tor network.
>>
>
> Is this an issue on all devices, or just some of them? Perhaps oorbot
> could refuse to run, or at least display a warning if it looks like the
> device is flaky.
>
-- 
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

