Delivery-Date: Sun, 02 Nov 2014 22:42:17 -0500
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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,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 71A091E050E;
	Sun,  2 Nov 2014 22:42:16 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id D9C7931570;
	Mon,  3 Nov 2014 03:42:09 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 45C8B3126F
 for <tor-talk@lists.torproject.org>; Mon,  3 Nov 2014 03:42:06 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 5Bu_Mw7zD6_V for <tor-talk@lists.torproject.org>;
 Mon,  3 Nov 2014 03:42:06 +0000 (UTC)
Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com
 [IPv6:2a00:1450:4010:c04::22e])
 (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 E254430F49
 for <tor-talk@lists.torproject.org>; Mon,  3 Nov 2014 03:42:05 +0000 (UTC)
Received: by mail-lb0-f174.google.com with SMTP id z11so6645694lbi.19
 for <tor-talk@lists.torproject.org>; Sun, 02 Nov 2014 19:42:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=6u7vkxcWV+Bfh5rPq21Yt1cWg1fD98M1MEXHpVXKmFE=;
 b=xQ8BelVXNHXx2Uoe7pmftNMu70xKNO18k4cUtrG4HUJyjKXr+MWI80/b8f185BcOLJ
 EWTYbPyLPdQfEmyT/FA2mW29FOhrh17mCDQM9j2fI3fPHEcQDBe8iuG61hJzXhxh06CM
 +eTslI8fAkp1WoDJP/FJFq1ZiCoum2eNqgAMGbCjxQYpF6pEm+AsZFkHTCrQB0AZSlp9
 XzpEUMS8qnYgZysn5Ieswq41ZRIcG4IjVirwXZTgpFrMMWeCqQwzc2a18hPA1VX0dJ2T
 WLtLq7neSlgmk7aOutPZNdJJbpLiTGgMdLFAcRfIKdZXWZLWIatwzSJsPgMw/dfsysSa
 7oUQ==
MIME-Version: 1.0
X-Received: by 10.112.141.104 with SMTP id rn8mr47654071lbb.87.1414986122644; 
 Sun, 02 Nov 2014 19:42:02 -0800 (PST)
Received: by 10.112.156.225 with HTTP; Sun, 2 Nov 2014 19:42:02 -0800 (PST)
In-Reply-To: <2433995.BO4utDXSYs@ncpws04>
References: <7488606.2oxgLGVBPl@ncpws04>
 <CAJVRA1QJ26Vtjt57N4Ducw3LV=MxnqaoGj0DY6L2D4-5vq8rxw@mail.gmail.com>
 <2433995.BO4utDXSYs@ncpws04>
Date: Sun, 2 Nov 2014 19:42:02 -0800
Message-ID: <CAJVRA1SE8jQs+ZDG426G5vdExikL8xxGT2KuvRz8RtaBPqfM3Q@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: tor-talk@lists.torproject.org, lth <lth@reclaim-your-privacy.com>
Subject: Re: [tor-talk] Cloak Tor Router
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>

On 11/2/14, Lars Boegild Thomsen <lth@reclaim-your-privacy.com> wrote:
> ...
> Doesn't this already exist?

there is also the clients behind NAT issue for stream isolation,
  e.g. clients[1-N...] -> WiFi Router -> Cloak -> ISP -.

it would be useful to document the list of these concerns somewhere,
perhaps on the Transparent Proxy wiki page. (i can do this later, if
anon doesn't beat me to it :)

---

as for lightweight builds, you may find the tor ramdisk effort
useful*, and at runtime, kernel tuning (e.g.
/proc/sys/net/ipv4/tcp_mem) and enabling ConstrainedSockets with a
desired ConstrainedSockSize.  this would only be necessary if memory
pressure truly is very tight.

64M is enough for Tor as client and hidden service or two, but will
have trouble with some pluggable transports and won't be a useful
relay.  the GeoIP database for friendly grouping by country can be
problematic as well, and may require some selective vfs pressure.

more later,


best regards,
-- 
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

